ExecuFunction
Wire ExecuFunction into your IDE so the agent shares one executive-function layer for tasks, calendar, notes, code search, and lightweight CRM.
Overview
ExecuFunction MCP is an MCP server for the Build phase that connects your IDE agent to tasks, calendar, knowledge, code indexing, and CRM on ExecuFunction.
What is this MCP server?
- Tasks, calendar, and knowledge base reachable from MCP tool calls
- Code indexing for context-aware answers inside the IDE
- Lightweight CRM for founder-led sales and follow-ups
- npm @execufunction/mcp-server v1.0.1 with npx runtime hint
- Auth via EXF_API_URL plus EXF_PAT personal access token
- Server version 1.0.1 (title ExecuFunction)
- Transport: stdio via npm @execufunction/mcp-server
- 2 required env vars: EXF_API_URL, EXF_PAT
What problem does it solve?
Solo builders fragment context across the IDE, calendar, notes, and CRM, so agents cannot act on what you actually need to do today.
Who is it for?
Founders who already use or plan to host ExecuFunction and want one MCP bridge for productivity plus light CRM from the agent.
Skip if: Teams wanting only Git-native issues, or builders unwilling to create ExecuFunction PATs and depend on an external EXF API.
What do I get? / Deliverables
After registering the server with EXF_API_URL and EXF_PAT, your agent can read and update unified executive-function data from the same workflow where you code.
- Unified agent access to tasks, calendar, and knowledge
- Code-aware retrieval via ExecuFunction indexing
- CRM-style contact context during coding sessions
Recommended MCP Servers
Journey fit
ExecuFunction is canonically shelved under Build agent-tooling because it extends the coding agent’s reachable workspace, yet it supports planning and ops across the journey. Agent-tooling is where MCP servers that unify tasks, knowledge, and repo context belong in a solo builder’s stack.
How it compares
Hosted executive-function MCP hub, not a single-purpose GitHub or Notion-only integration.
Common Questions / FAQ
Who is ExecuFunction MCP for?
Solo and indie developers using MCP clients who want agent access to ExecuFunction tasks, calendar, knowledge, code index, and CRM.
When should I use ExecuFunction MCP?
Use it whenever you work from the IDE across planning, building, and follow-ups and need the agent to see the same task and contact graph you use.
How do I add ExecuFunction MCP to my agent?
Install @execufunction/mcp-server via npx stdio, set EXF_API_URL to your instance, and set secret EXF_PAT from ExecuFunction Settings → Developer → Access Tokens.