MCP

Overview

Apender exposes a stdio MCP server that forwards tool calls to the API. The repo stays on disk; intent, answers, and optional project metadata are sent over HTTPS. Host-specific file locations: Integration guides.

Environment variables

Set these in the MCP host config (Cursor, Claude Code, etc.):

APD_API_URL

API base URL from Dashboard → API keys. This is where the MCP server sends requests — not your app’s URL.

APD_API_KEY

The apd_live_… key from the same page. Env or secret store only — not git.

APD_WORKSPACE_ROOT

Absolute path to the git repo root. Used for project context sent with sessions.

Example MCP server block (replace placeholders):

{
  "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"
      }
    }
  }
}

Tools the agent can call

runtime_startSession

Start engineering or simple session from intent

runtime_message

Gateway message / follow-up

runtime_answerQuestion

Submit user answers when halted

runtime_getSession

Poll session state

runtime_getSpecification

Fetch compiled specification

runtime_getSimpleTaskBrief

Simple-path brief

runtime_syncProjectIntelligence

Refresh PIG for workspace

runtime_detectProjectIdentity

Detect git remote / workspace identity

runtime_discoverRepository

Discovery-only pass

runtime_getProjectGraph

PIG snapshot for session

Typical workflow

1. Agent calls runtime_startSession with the intent string.
2. If the response asks for input, the agent surfaces questions in chat, then calls runtime_answerQuestion.
3. When complete, the agent fetches the plan and edits the repo with normal file tools.