Drive TaskNest from Claude — or any AI agent

TaskNest ships a native MCP (Model Context Protocol) server — not a bolt-on. Your agent can create projects, plan sprints, file and update tasks, search your wiki, and run automations through 47 first-class tools, with the same permissions as your account.

Connect in three steps

1. Sign in and grab your access token. Your MCP session uses the same Bearer token as the app — sign in at tasknest.in and copy your token from Settings → API.
2. Point your MCP client at the endpoint. One JSON-RPC 2.0 endpoint, standard tools/list + tools/call.
3. Ask your agent to do real work. "Create a sprint for next week and move the open bugs into it" — the agent calls the same services the app uses, so events, automations and notifications all fire normally.

The endpoint

# JSON-RPC 2.0 over HTTPS — list the available tools
curl -X POST https://tasknest-production-3d3d.up.railway.app/api/mcp \
  -H "Authorization: Bearer <your-token>" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

# Call a tool — e.g. create a task
curl -X POST https://tasknest-production-3d3d.up.railway.app/api/mcp \
  -H "Authorization: Bearer <your-token>" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call",
       "params":{"name":"tasks.create",
                 "arguments":{"projectId":"<id>","title":"Fix login bug","priority":"High"}}}'

What your agent can do

A sample of the 47 tools (grouped by domain):

Prefer plain HTTP?

The same surface is available as a REST public API (personal API keys with read/write scopes — Settings → API), a GraphQL endpoint at /api/graphql, and HMAC-signed outbound webhooks for task and project lifecycle events. Inbound, a Zapier/Make-style webhook can create tasks from any tool.