Skip to content
AppHandoff

Hosted MCP Server

Hosted MCP server with live project context for AI coding agents

AppHandoff's MCP server exposes over 30 tools that give AI agents structured access to handoff tickets, roles, milestones, published API contracts, and deploy checks — no file scraping, no stale documentation.

What is AppHandoff's MCP server?

An MCP server is a service that exposes tools and resources to AI coding agents through the Model Context Protocol — the open standard originally developed by Anthropic. AppHandoff's hosted MCP server is the coordination surface for your project: handoff tickets with roles, milestones, agent-published API contracts, and deployment status.

Instead of asking an agent to infer project state from raw files or Slack threads, the AppHandoff MCP server delivers machine-readable answers to the questions agents actually ask: what tickets are open, what is assigned to which role, what contracts are published, and what shipped.

The server is hosted — no Docker containers, no local proxies, no process to keep running. Connect once via OAuth and every compatible agent gets immediate, scoped access to your project context.

  • 30+ tools covering tickets, roles, milestones, and contracts
  • Hosted endpoint — no local server required
  • OAuth 2.1 authentication with per-project scoping
  • Compatible with Cursor, Claude, Windsurf, and any MCP client

Structured coordination state, not raw diffs

Unlike raw file access or code search, MCP tools return structured, contextually relevant information. When an agent asks for its workload, it receives tickets with roles, acceptance criteria, and implementation notes — not a raw diff it would need to interpret on its own.

The server supports OAuth authentication, session persistence, and per-project access controls. Agents can only see projects their user has access to, and every tool call is logged for auditability.

  • Project summary bootstrap with rules and role context
  • Contract publishing and confirmation between agents
  • Milestones and role-lifecycle tracking
  • Ticket lifecycle, audit trail, and deployment status tools

Built for multi-agent coordination

The same MCP surface works for Cursor, Claude, Lovable, and other compatible clients simultaneously. Multiple agents working on the same project see the same ticket state, the same roles, and the same published contracts — eliminating the context drift that typically causes duplicate work or conflicting implementations.

The AppHandoff MCP server supports both Streamable HTTP and SSE transports, so it connects to the full spectrum of MCP-compatible clients without protocol negotiation on your end.

Connect in under five minutes

Add the AppHandoff MCP server endpoint to your client's MCP configuration, approve the OAuth sign-in that opens in your browser, and your agent has immediate access to live project context.

The server is always on — backed by two always-running machines — so agents that reconnect mid-session, restart, or run on a schedule pick up exactly where they left off without re-authentication.

  • Single endpoint URL — no port forwarding or local tunnels
  • Session persistence across agent restarts
  • API-key access for automated pipelines via the REST API
  • Streamable HTTP and SSE transport support

FAQ

What is an MCP server?

An MCP server is a service that exposes tools, resources, and prompts to AI models through the Model Context Protocol. It acts as the bridge between an AI coding agent and the external data sources or capabilities the agent needs — in AppHandoff's case, handoff tickets, roles, milestones, and published API contracts.

Which MCP clients does AppHandoff support?

Any client that implements the Model Context Protocol. This includes Claude Desktop, Cursor, Windsurf, and the Claude API with tool use. AppHandoff supports both Streamable HTTP and SSE transports, covering the full range of current MCP client implementations.

Do I need to run a local MCP server?

No. AppHandoff's MCP server is fully hosted. There is no Docker container, local process, or tunnel to maintain. Add the endpoint URL to your client configuration, authenticate once, and the server handles the rest.

How is access controlled?

Each user authenticates via OAuth. The server enforces per-project access so agents only see the projects their user is authorised to access. All tool calls are logged for audit purposes.

What tools does the MCP server expose?

The server exposes over 30 tools covering project context (summaries, rules, milestones), contract publishing and confirmation, handoff ticket management (create, update, close tickets), agent session coordination, and deployment status. A full reference is available in the documentation.

Related guides

All AppHandoff featuresThe full coordination layer — shared Kanban, agent handoffs, plan-before-code review, and MCP project context in one place.What is an MCP Server?The definitive guide to Model Context Protocol — how it works, the three primitives, and how to set up your first connection.Best MCP Servers for Claude CodeThe top MCP servers to connect to Claude Code — GitHub, PostgreSQL, Supabase, Linear, AppHandoff, and more.Connect Claude Code, Cursor & CodexStep-by-step walkthrough: one URL, one OAuth sign-in, and your first ask_apphandoff call.MCP for LovableHow Lovable-built frontends connect to the AppHandoff MCP surface for backend coordination.MCP Server ArchitectureDeep dive into MCP protocol internals — JSON-RPC 2.0, Streamable HTTP, session management, and scaling.MCP Server ExamplesSurvey of production MCP servers — filesystem, GitHub, PostgreSQL, Linear, Slack, and AppHandoff.

Next step

See the full workflow in context

Explore pricing and comparisons from the same public AppHandoff site before connecting your first project.

View pricingCompare approaches