Cursor

How it works

Cursor spawns the Apender MCP server as a child process. The agent calls Apender tools, then edits files with Cursor’s normal tools.

Architecture

Repo + Cursor agent → MCP (stdio) → Apender API → plan back to the agent.

Configuration

Cursor Settings → MCP, or .cursor/mcp.json in the open project. Add the apender entry under mcpServers. Optional: copy the default rule from Docs → MCP → Cursor rules into .cursor/rules/apender.mdc.

Example server block — adjust paths as needed. Full reference: MCP configure.

{
  "mcpServers": {
    "apender": {
      "command": "node",
      "args": ["/absolute/path/to/apender-mcp-server"],
      "env": {
        "APD_API_URL": "<API base URL from Dashboard → API keys>",
        "APD_API_KEY": "apd_live_your_key",
        "APD_WORKSPACE_ROOT": "/absolute/path/to/git/repo"
      }
    }
  }
}

Cursor rules

After MCP is connected, add a project rule so the agent calls Apender before implementation. Copy the default snippet from MCP → Cursor rules into .cursor/rules/apender.mdc.

Authentication

Set APD_API_KEY and APD_API_URL from Dashboard → API keys in the env block.

Create keys in Dashboard → API keys.

Workspace root

Set APD_WORKSPACE_ROOT to the same folder opened in Cursor (git root).

Example

In agent chat: "Add rate limiting to auth routes." The agent calls Apender tools, then applies the plan in the repo.

Troubleshooting

Unauthorized from runtime tools

Check APD_API_KEY and APD_API_URL match Dashboard → API keys. Do not use Bearer in MCP env.

Tools not listed after config change

Reload MCP from the command palette or restart Cursor.