GlassFrog MCP Server

GlassFrog

GlassFrog is the standard platform for Holacracy governance. Nested circles with distributed authority — no traditional hierarchy. Credentials are bound on the connection.

Data Model

• Circles — teams that nest hierarchically. Name, strategy, linked roles. Top-level is the "Anchor Circle."
• Roles — defined responsibilities within circles. Core roles have is_core: true. Purpose, domains, accountabilities.
• Assignments — maps people to roles. A person can hold multiple roles across circles.
• People — organization members with name, email, linked circle/role IDs.
• Projects — deliverables tracked against roles. Status: Current/Waiting/Future/Done/Archived. Full CRUD supported.
• Metrics — measurable outcomes for roles. Frequency: Weekly/Monthly/Quarterly. Full CRUD supported.
• Checklist Items — recurring tasks within a role. Frequency: Weekly/Monthly/Quarterly. Full CRUD supported.
• Custom Fields — extra metadata on roles or people (read-only via API).

Capabilities

Read: Enumerate circles, roles, assignments, people, projects, metrics, checklist items, custom fields.

Write (Projects): Create with description/circle_id/role_id, update status/description/waiting info, delete permanently or archive via status update.

Write (Checklist Items): Create with description/circle_id/frequency, update description/frequency, delete.

Write (Metrics): Create with description/circle_id/frequency, update description/frequency/link, delete.

Common Workflows

• Add a project: Enumerate circles and roles to get IDs → create a project with description, circle_id, role_id.
• Complete a project: Enumerate projects to find the ID → update status to "Done."
• Track a new metric: Enumerate circles to find the right circle ID → create a metric with description and frequency.
• Who does what?: Enumerate assignments → cross-reference person IDs with the people directory and role IDs with the roles directory.

Gotchas

• Linked responses — all responses include a links object with IDs referencing other entities. Fetch the linked entity to resolve names.
• JSON Patch for updates — update operations use JSON Patch format internally; rely on the typed update parameters rather than hand-building patch documents.
• No pagination — directory reads return all records in a single response.
• Delete is permanent — deleted projects/metrics/checklist items are removed from the database entirely. Use status "Archived" for projects if you want to keep a record.
• circle_id and role_id required for creates — projects need both; checklist items and metrics need circle_id and optionally role_id.