↹ MCP-native

Don’t integrate with our agents. Bring your own.

Projoint speaks the Model Context Protocol — the open standard your AI tools already use. Instead of waiting for us to build a connector, point your client at Projoint and go.

One MCP endpoint. Every client you already use.

We expose a full MCP server at POST /mcp. Claude Code, Cursor, Cline, or your own client authenticate with a Personal Access Token and get the same actions you have in the UI — read tasks, post comments, change status, start timers, run agents.

POST https://api.projoint.tech/mcp
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "create_task",
    "arguments": {
      "projectKey": "WEB",
      "title": "Plan v1 launch",
      "dueDate": "2026-05-22",
      "priority": "high"
    }
  }
}
→ WEB-128 · assigned to you · 124 ms

Direct connectors.

For the tools you don’t drive through MCP, native connectors. We badge honestly — only “available” works today; the rest is on the roadmap.

GitHub

Available

Link tasks to PRs and issues; trigger agents on PR events.

Calendar (iCal)

Available

Subscribe to your tasks and due dates from any calendar app.

REST API + PATs

Available

A public REST API with Personal Access Tokens — script anything.

Webhooks

Available

Outbound webhooks fire on the events you care about.

Slack

Coming soon

Notifications and slash-commands into your channels.

Linear / Jira import

Coming soon

Bring your existing backlog over without retyping it.

Live availability is always shown inside the app under Settings → Integrations. Want a connector that isn’t here? Ask for it.

Build your own — the API is public.

A public REST API with Personal Access Tokens and outbound webhooks means anything you can do in Projoint, you can automate. The MCP surface is the AI-native path on top of the same foundation.

Ship the next thing faster.

Free for ten users. No card required. AI optional.