ExecuFunction MCP Server

A Model Context Protocol server that exposes ExecuFunction tools to IDE clients like Cursor, Claude Desktop, and VS Code.

Quick Start

1. Create a Personal Access Token

1. Go to ExecuFunction → Settings → Developer → Access Tokens
2. Click "Create Token"
3. Name it (e.g., "Cursor MCP")
4. Select scopes: mcp:* (or specific scopes like projects:read, tasks:write)
5. Save the token immediately - it's only shown once!

2. Configure Your MCP Client

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "execufunction": {
      "command": "npx",
      "args": ["@execufunction/mcp-server"],
      "env": {
        "EXF_API_URL": "https://execufunction.com",
        "EXF_PAT": "exf_pat_your_token_here"
      }
    }
  }
}

Cursor

Add to your Cursor MCP settings:

{
  "execufunction": {
    "command": "npx",
    "args": ["@execufunction/mcp-server"],
    "env": {
      "EXF_API_URL": "https://execufunction.com",
      "EXF_PAT": "exf_pat_your_token_here"
    }
  }
}

VS Code

Configure in your MCP extension settings.

3. Restart Your IDE

After configuration, restart your IDE to load the MCP server.

Available Tools

Projects

Tasks

Knowledge / Notes

People

Calendar

Codebase Indexing

Code History & Expertise

Code Memories

Vault / Secrets

Entity Graph

Document Upload

Datasets (feature flag: DATASETS_ENABLED=true)

Ontology (feature flag: DATASET_ONTOLOGY_ENABLED=true)

Usage Examples

1. Get project context and create a task

User prompt: "Get context for my auth project and create a task to fix the token refresh bug"

Tools invoked:

1. project_list — Lists projects to find the auth project
2. project_get_context — Retrieves tasks, notes, and signals for the project
3. task_create — Creates a new task with title, description, and project linkage

Result: The AI reads existing project context (open tasks, recent notes) to avoid duplicates, then creates a well-scoped task linked to the correct project.

2. Semantic code search

User prompt: "Find where we handle webhook signature verification"

Tools invoked:

1. codebase_search — Searches indexed code for "webhook signature verification"

Result: Returns ranked code chunks with file paths, line numbers, and surrounding context. The AI can then read the matched files to answer follow-up questions.

3. Knowledge search and note creation

User prompt: "Search for our deployment process and create a note summarizing the steps"

Tools invoked:

1. note_search — Searches the knowledge base for "deployment process"
2. code_memory_search — Searches stored code facts for deployment-related memories
3. note_create — Creates a new note with a markdown summary of the deployment steps

Result: The AI synthesizes information from existing notes and code memories into a single reference note, linked to the relevant project.

Resources

The server also exposes project context bundles as MCP resources:

• exf://projects/{id}/context - Full context bundle for a project

Environment Variables

Development

# Install dependencies
npm install

# Run in development mode
npm run dev

# Test with MCP Inspector
npm run inspect

# Build for production
npm run build

Security

• PATs are stored as SHA-256 hashes - plaintext is never stored
• Tokens can be revoked at any time from ExecuFunction Settings
• Use minimal scopes for your use case
• Never commit tokens to version control

Scopes

Troubleshooting

"EXF_API_URL environment variable is required"

Make sure you've configured the env section in your MCP client config.

"Invalid token"

1. Check that your token starts with exf_pat_
2. Verify the token hasn't been revoked
3. Check the token hasn't expired

Tools not appearing

1. Restart your IDE after configuration changes
2. Check IDE logs for MCP errors
3. Try running npm run inspect to test the server directly

License

MIT