Skip to main content

MCP server

  • Updated

The Axify MCP server connects your AI assistant — Claude, Cursor, Codex, and others — directly to your Axify workspace. You ask in plain language and the assistant answers with data pulled from your projects, teams, and metrics.

This guide covers the following steps :

  1. Before you start
  2. Connecting Axify to Claude Desktop
  3. Connecting Axify to Claude Code
  4. Connecting Axify to ChatGPT
  5. Connecting Axify to Cursor
  6. Other MCP clients
     
  7. What you can ask Axify
  8. Troubleshooting

Before you start

  • You need an active Axify account and to be signed in to Axify in your browser.
  • Authentication uses OAuth. There is no API key to generate or paste.
  • The server respects your Axify permissions — your assistant sees the same data you would see in the app.
  • The Axify MCP server URL is :
https://mcp.axify.io/mcp

Axify is compatible with any MCP client that supports HTTP transport and OAuth. The four most popular clients are documented below; for others, see Other MCP clients.


Connecting Axify to Claude Desktop

  1. Go to Settings → Connectors and click the + button.
  2. Select Add custom connector.

  3. In the Remote MCP server URL field, enter :

    https://mcp.axify.io/mcp
  4. In the Name field, enter Axify.
  5. Click Add.
  6. Sign in to Axify in the browser window that opens. Axify is now available in the tools menu.

[Screenshot]


Connecting Axify to Claude Code

  1. Run the install command in your terminal :

    claude mcp add axify-mcp --transport http https://mcp.axify.io/mcp
  2. Sign in. The first time Claude Code calls an Axify tool, your browser opens for OAuth — sign in to Axify and authorize access.

[Screenshot ]


Connecting Axify to ChatGPT

Custom MCP connectors are available on ChatGPT Business, Enterprise, and Edu plans.
 

  1. Open Settings → Connectors in ChatGPT.
  2. Click Create to add a new connector.

  3. In the MCP server URL field, enter :

    https://mcp.axify.io/mcp
  4. In the Name field, enter Axify.
  5. Click Create.
  6. Sign in to Axify in the browser window that opens. Axify is now available as a connector in your conversations.

[Screenshot ]


Connecting Axify to Cursor

  1. Open Settings → MCP & Integrations and click New MCP Server to open mcp.json.

  2. Add this entry (or merge it with your existing configuration) :

    {
  "mcpServers": {
    "axify": {
      "url": "https://mcp.axify.io/mcp"
    }
  }
}
  3. Sign in. Save the file, click Needs login on the Axify entry, and authorize access in the browser. The indicator turns green when Axify is ready.

[Screenshot ]


Other MCP clients


The Axify MCP server follows the official Model Context Protocol standard. Any client supporting HTTP transport and OAuth (Windsurf, Zed, Continue, custom agents…) connects with these parameters :

Parameter Value
Transport type HTTP (also called Streamable HTTP or Remote MCP)
URL https://mcp.axify.io/mcp
Authentication OAuth (browser window opens on first connection)

For clients that use a JSON config file :

{
  "mcpServers": {
    "axify": {
      "url": "https://mcp.axify.io/mcp"
    }
  }
}


What you can ask Axify


A few starter prompts, grouped by topic.

DORA and engineering performance

  • "What did our deployment frequency look like last quarter?"
  • "Compare lead time across the Platform and Mobile teams."
  • "Where did mean time to recovery degrade over the last 90 days?"

Pull requests and code review

  • "Which PRs have been waiting on review for more than 3 days?"
  • "Who has the longest cycle times this sprint?"
  • "What was the average review time across engineering last month?"

Deliverables and roadmap

  • "Which deliverables are at risk for the Atlas team this week?"
  • "Give me a status update on the Q2 roadmap."
  • "What is blocking the Mobile squad's current initiative?"

Retrospectives and team signals

  • "Summarize the blockers raised in last month's retrospectives."
  • "What themes keep coming up in our retros this quarter?"
  • "Action items from the Platform team's last three retros."


Troubleshooting

Symptom Likely cause / Recommended resolution
Authentication never completes Make sure you are signed in to Axify in the same browser that opens. If the problem persists, remove the server from your MCP client and start over.
Some teams or data are missing from responses The MCP server applies the same permissions as the web app. Ask an Axify administrator to verify your access.
The assistant doesn't seem to use Axify to answer Some clients let the AI decide whether to invoke an MCP tool. Be explicit : "Use Axify to…" or "Look it up in Axify…" usually steers it in the right direction.
The client refuses the connection or returns an HTTP error Make sure your client supports HTTP transport (sometimes called Streamable HTTP or Remote MCP) and is up to date.

 

Still stuck? Email help@axify.io with the MCP client you are using, the step where the problem occurs, and the error message.

Related articles