Exponential MCP
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Exponential MCP
Connect Claude to your Exponential workspace. Manage projects, actions, and OKRs directly from Claude.
Quick Start
You need Node.js 18 or later and an Exponential account. Setup is two steps: create an agent, then connect your app.
1. Create an Agent
Open exponential.im/settings/agents/new:
Name the agent after the app it will run in (for example "Claude")
Pick the workspaces it may work in
Click Create agent and copy the key (
exp_agent_…) — it is shown once
The agent is its own identity: what Claude does in Exponential is attributed to it, not to you.
2. Connect Your App
Find your app below. <key> is the key from step 1.
Claude Desktop
npx exponential-mcp initPaste the key when prompted, then quit and reopen Claude Desktop. init saves the key on this machine and adds the server to Claude Desktop's config file on macOS, Windows and Linux.
Claude Code
claude mcp add --scope user exponential -e EXPONENTIAL_API_KEY=<key> -- npx -y exponential-mcp serve--scope user makes the server available in every project. Leave it out to add the server to the current project only.
Cursor
Add to ~/.cursor/mcp.json (every project) or .cursor/mcp.json (one project):
{
"mcpServers": {
"exponential": {
"command": "npx",
"args": ["-y", "exponential-mcp", "serve"],
"env": { "EXPONENTIAL_API_KEY": "<key>" }
}
}
}VS Code
Add to .vscode/mcp.json. VS Code names the top-level key servers, not mcpServers:
{
"servers": {
"exponential": {
"command": "npx",
"args": ["-y", "exponential-mcp", "serve"],
"env": { "EXPONENTIAL_API_KEY": "<key>" }
}
}
}Codex
Add to ~/.codex/config.toml:
[mcp_servers.exponential]
command = "npx"
args = ["-y", "exponential-mcp", "serve"]
env = { EXPONENTIAL_API_KEY = "<key>" }Any Other MCP Client
Run the command npx with the arguments -y exponential-mcp serve, and set the environment variable EXPONENTIAL_API_KEY to your key. The server speaks MCP over stdio.
3. Ask
Restart the app, then try: "What's on my plate today?"
Related MCP server: Todoist Meeting MCP
One Key per App
Create a separate agent for each app, so that what each app does in Exponential is attributed to its own agent. The config blocks above do this: each one carries its own key in EXPONENTIAL_API_KEY.
init works differently. It saves one key on the machine, and any app whose config has no EXPONENTIAL_API_KEY falls back to it. EXPONENTIAL_API_KEY always overrides the saved key.
To give Claude Desktop its own key, add "env": { "EXPONENTIAL_API_KEY": "<key>" } to the exponential entry in its config file (see Claude Desktop by Hand). Re-running init rewrites that entry, including its env.
A personal API key from Settings → API keys also works in place of an agent key, but then the app acts as you.
Self-Hosted Exponential
Point the server at your own instance with npx exponential-mcp init --base-url https://your-host, or set EXPONENTIAL_API_URL next to EXPONENTIAL_API_KEY in the app's config.
What Claude Can Do
Once connected, Claude can:
List projects – "What projects am I working on?"
View actions – "Show my active tasks"
Create actions – "Add a task to call John tomorrow"
Complete actions – "Mark the report task as done"
View OKRs – "What are my Q1 goals?"
Search – "Find anything related to Kenya"
Work the CRM – "Log that I emailed Keily today" / "Move the Onionpress deal to Proposal"
Run the product backlog – tickets, features, epics, stories, pages and decisions
Track time – log, confirm and report on the day
Claude Desktop by Hand
npx exponential-mcp init edits Claude Desktop's config file for you. To do it yourself, open the file for your platform:
Platform | Config file |
macOS |
|
Windows |
|
Linux |
|
Add the exponential entry under mcpServers, keeping any servers already there:
{
"mcpServers": {
"exponential": {
"command": "npx",
"args": ["-y", "exponential-mcp", "serve"],
"env": { "EXPONENTIAL_API_KEY": "<key>" }
}
}
}Then quit and reopen Claude Desktop.
If you installed Node with nvm, fnm, asdf or similar, a bare npx will not work here: Claude Desktop does not start servers with your shell's PATH. Use the entry that npx exponential-mcp doctor prints. It names npx by its full path and puts Node's directory on PATH. init writes that same entry.
Troubleshooting
Start with npx exponential-mcp doctor. It checks the saved key and Claude Desktop's config, and prints a config entry that works on your machine.
Symptom | Fix |
The tools don't appear | Quit the app completely and reopen it. MCP servers load only at startup. |
Claude Desktop logs | Node is outside the system |
It worked, then stopped starting | Versions before 0.13.1 pointed Claude Desktop at npx's cache, which npx may delete. Run |
On Windows, | Versions before 0.13.1 wrote to a file Claude Desktop does not read. Run |
| npx's cache holds a half-finished install. Delete the |
The key is rejected, or the app acts as the wrong agent |
|
You want the newest version |
|
Commands
# Initialize with an agent key
exponential-mcp init
# Show current config
exponential-mcp config
# Diagnose local setup
exponential-mcp doctor
# Start server manually (usually not needed)
exponential-mcp serveAvailable Tools
Tool | Description |
| List all workspaces |
| Agent context for a workspace (and project): instructions, decisions, ADRs. Guidance, not authority |
| The published Exponential method. Guidance, not authority |
| List projects (optionally by workspace) |
| One project in full: linked objectives & key results, DRI, team, dates |
| Rename, change status/priority, set dates, re-link to OKRs |
| List actions/tasks (filter by project or status; no date filtering) |
| What's on your plate now — overdue / today / inbox, across all workspaces |
| Why the overdue pile is that size: bulk-created cohorts vs real debt |
| Create a new task (supports natural language) |
| Rename, re-prioritise, move project, or set dates (incl. |
| Amnesty: clear dates, back to the project backlog untimed |
| Move actions to a new do-date |
| Mark an action as done |
| List objectives, flat or as the annual → quarterly tree |
| List key results, grouped by objective or flat |
| List meetings, newest first, with a summary preview (no notes/transcript) |
| One meeting with notes; transcript on request |
| Record a meeting from a transcript or notes |
| Edit title, description, summary, date, or replace notes |
| Add to a meeting's notes without overwriting them |
| Search across everything |
Domain tools
Alongside the tools above, every part of the Exponential SDK is exposed as one tool per domain, so the MCP server can do anything the SDK and CLI can:
actions · projects · workspaces · positions · goals · key_results · meetings ·
time · decisions · contacts · organizations · deals · products ·
features · scopes · requirements · areas · stories · epics ·
tickets · labels · pages · databases · comments
Each takes { operation, params }. The tool description lists every operation
with a one-line signature; operation: "describe" returns the full parameter
schema for one operation (params: { operation: "create" }) or all of them.
Invalid params come back as an error that includes the expected schema.
{ "operation": "add_interaction",
"params": { "contactId": "…", "type": "EMAIL", "direction": "OUTBOUND", "subject": "Intro" } }comments covers comments on actions, features, pages, goals and tickets — pass
target to choose which.
positions is a workspace's roles & responsibilities — the Positions on the
settings page: list, create, update, set_holders, delete, and import_many
(upsert by title, with a dry run). Writes need your own API key, not an agent
key, and owner/admin, except that a holder may edit their own Position's remit.
databases is the typed write path for tables inside pages (ADR-0078): a
database is a block in a page body and each row is a page. Values are typed
per property — a select takes an option name, a date an ISO string, a person
a user ID — and a wrong value is refused naming the property, so call get
first to learn the schema. Reading the page with pages shows the table.
Asking about the day
Use get_todays_actions, not get_actions, for anything about today,
priorities, or what the user is behind on. get_actions has no date filtering
at all, so it cannot distinguish overdue work from anything else.
When there is a lot of overdue work, follow up with get_overdue_triage
before proposing what to do. A large overdue count is usually a few bulk writes
— a generated project plan stamped every row with one timestamp — not a large
number of missed commitments. Those are cohorts, and the honest disposition
is defer_actions (amnesty); reschedule_actions would just re-inflict the
same pile tomorrow. Individually-dated loose actions are the ones that
deserve a real decision.
Annotations
Every tool carries MCP tool annotations: a title, readOnlyHint and
destructiveHint. A domain tool is read-only only when every operation reads,
and destructive when any operation deletes. No hand-written tool deletes
anything.
Using the tools in your own server
The tool registry is also exported on its own, as exponential-mcp/tools, so
another server can offer the same tools over a different transport. The
hosted endpoint in the Exponential app is built on it. Importing it has no side
effects: it reads no config, touches no files and never exits the process. You
build the ExponentialClient, so you choose who the tools act as.
import { ExponentialClient } from 'exponential-sdk';
import { listTools, callTool } from 'exponential-mcp/tools';
const client = new ExponentialClient({ token: process.env.EXPONENTIAL_API_KEY!, apiUrl: 'https://www.exponential.im' });
listTools(); // Tool[] for tools/list
await callTool(client, 'get_workspaces', {}); // CallToolResult for tools/calllistTools(options?)returns every tool intools/listorder.callTool(client, name, args, options?)runs one tool. A failure comes back as a result withisError: truerather than a throw.The three run tools (
report_progress,ask_owner,finish_run) exist only for a session serving an Agent run. They are listed and callable only whenoptions.runContext({ runId, runnerId? }) is passed; leave it out otherwise.
The stdio server (exponential-mcp serve) calls the same two functions, so both
offer the same tools from the same release.
Development
# Clone the repo
git clone https://github.com/exponential-im/exponential-mcp
cd exponential-mcp
# Install dependencies
npm install
# Build
npm run build
# Run locally
npm startContributing
Who merges: the PR-Agent auto-merge gate, or James
.github/workflows/pr-agent-automerge.yml squash-merges a PR into main once CI
(Build, typecheck & test) is green and PR-Agent left nothing blocking on the latest
commit. Agent sessions do not merge PRs.
PR-Agent runs review-only: GLM 5.3 through OpenRouter, one call per push. It doesn't
rewrite descriptions or post code suggestions. What blocks is a review finding tagged
[blocker] or left untagged, or a security concern. Fix those; [minor] findings don't
hold the merge. Every push is reviewed again and paid for, so batch fixes into one push
rather than pushing each one separately. The model and house rules are in .pr_agent.toml;
PR-Agent reads that file from main, so editing it on a branch changes nothing until merged.
Never run
gh pr merge, and never pass--mergeto/ship-thisor/ship-ticket. Open the PR, apply PR-Agent's findings, push, and stop at "in review". The gate (or James) merges.Never add the
pr-agent-acklabel. It means "James saw the blocker and is merging anyway". Only James applies it, and the gate ignores it from anyone else.A PR you can't get past the gate is left for James with a comment saying what blocks it and why you could not fix it.
no-automergeon a PR keeps it human-only. Don't remove it.PRs from forks and PRs opened by bots are never auto-merged; James merges those.
exponential-sdk must be published before a PR that needs it
CI runs .github/scripts/check-sdk-pin.mjs before npm ci. It fails when the
exponential-sdk range in package.json has no published version on npm, when
package-lock.json pins a version that isn't on npm (or a local link or tarball), or when
the two files disagree. Publish the SDK first, then run npm install here and commit
package-lock.json. A version published in the last few minutes can lag the registry;
re-run the job.
.github/workflows/sdk-bump.yml checks npm hourly and opens a chore: bump exponential-sdk to <version> PR when there is a newer SDK. A bot opens it, so the gate leaves it for James.
License
GNU Affero General Public License v3.0 or later (AGPL-3.0-or-later). See LICENSE.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Connect Claude to your Platform7n workspaces: chat, links, work and decks. One-click OAuth.
Connect Claude to your Platform7n workspaces: chat, links, work and decks. One-click OAuth.
Create contacts, move deals, send proposals and invoices, read your inbox, from Claude or ChatGPT.
Connect Claude to Fathom meeting recordings, transcripts, and summaries
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI-native task and project management through natural language conversation with Claude, eliminating app-switching by letting you add actions, manage projects across multiple areas of focus, and maintain a GTD-style execution system directly in chat.1-
- AlicenseAqualityDmaintenanceConnects Claude to Todoist for transforming meeting notes into actionable tasks with inferred due dates and priorities. It enables full task lifecycle management, including creating subtasks, listing projects, and completing tasks through natural language.7MIT
- AlicenseNot gradedqualityDmaintenanceConnect Claude directly to your MindBacklog workspace to read PRDs, user stories, and real-time customer signals.MIT
- FlicenseNot gradedqualityDmaintenanceConnects Claude.ai to your Motion workspace, enabling task and project management via natural language.-