Skip to main content

​
Overview

The Candidate Profile platform is available as a remote Model Context Protocol (MCP) server. Use the REST API when you want direct HTTP control from your application. Use the MCP server when you want an MCP-compatible client to discover candidate data, call tools, and work through multi-step prompts without hand-orchestrating each endpoint.
Remote MCP endpoint
https://mcp.jonahanderson.me/mcp
Add this endpoint to an MCP-compatible client. The server exposes resources, tools, and a reusable prompt through a single remote URL.

​
What the server exposes

Resources

Read six JSON resources for candidate, experience, projects, availability, and resume data.

Tools

Call read tools for profile lookups and, when enabled, mutation tools for auth token and contact workflows.

Prompts and interactions

Start with the built-in summary prompt or try example workflows that show how a client can use the server.

REST API reference

Compare the MCP surface with the underlying HTTP endpoints that power the same data model.

​
Availability notes

  • Every registered resource returns application/json.
  • Read tools are annotated as read-only and idempotent.
  • Mutation tools are optional and only appear when the deployment enables them.
  • The MCP server uses the same underlying candidate profile data as the REST API.

​
First interaction

1

Connect the endpoint

Add https://mcp.jonahanderson.me/mcp to your MCP-compatible client.
2

Ask for a goal, not an endpoint

Start with a task such as “Summarize Jonah Anderson for a backend platform engineering role and include current availability.”
3

Let the client choose resources and tools

A typical flow might inspect the profile, check availability, and then pull supporting experience or project details.
Typical tool flow
get_candidate
get_availability
list_experience({ "current": true })
list_projects
If your client supports MCP prompts, candidate_profile_summary is the fastest first test. The full prompt reference and example workflows are in the interactions page.