CURSOR

Status: connects, tool calls not verified. Driven by hand, it authenticated and listed every tool, but no write-back was confirmed. It speaks the same protocol as the clients that are verified, so this page is worth following. If it works for you, or if it does not, say so and this line changes.

The Cursor app and the Cursor CLI read the same config file, so this page covers both. Where they differ is what happens after the file is saved, and the CLI has one extra gate that catches almost everybody.

1. Point it at the Hub

~/.cursor/mcp.json for every project, or .cursor/mcp.json for just this one

{
  "mcpServers": {
    "astryke-hub": {
      "type": "http",
      "url": "https://app.astryke.com/mcp"
    }
  }
}

2. Approve it in the browser

In the app: Settings, then Tools and MCP, and sign in from there.

Sign-in happens in a browser window your editor opens. There is no API key and nothing to paste back, so no secret ever lands in a chat window or on disk. Approving mints a token tied to that one machine, which you can revoke on its own later.

Do not open the server address in a browser yourself. It is an API endpoint, not a sign-in page. If you find yourself trying to authorize by hand, step 1 did not take and that is what to fix.

3. Check it worked

Ask your agent to call get_brief, or use the /catch-up command if your editor surfaces MCP prompts. On a new account you get an empty board. That is the correct answer, not a failure: Astryke does not invent a placeholder project. Tell the agent what you are working on and it fills it in.

4. Give it a reason to use the Hub

This is the step everyone skips. MCP is pull-only, so connecting gives your agent the ability to read your board and no reason to bother. Without a standing instruction the tools sit there and you carry on being asked what you were working on.

Append this to .cursor/rules/astryke.mdc, the file Cursor reads at the start of every session. Do not overwrite what is already in there.

# Astryke Hub

At the START of every session, call the get_brief tool from the
astryke-hub MCP server before answering anything about my projects.
It tells you what I am working on, what each project is waiting on,
and which decisions are already settled. Do not ask me what I was
doing - look first.

Before you finish meaningful work, call report_progress so the next
session knows what happened.

If you hit a fork only I can settle, call ask_question instead of
guessing.

Then read the file back and check the tool names are spelled exactly as above. On Windows, if your agent writes this file through PowerShell, a backtick before a letter is an escape character and will silently eat part of a tool name. A quoted get_brief has arrived on disk as get_brie, and nothing reports an error. The call just never works.

Your trial starts here

The 14 days begin when you connect your first agent, not when you sign up. Nothing is counting while you read this.

On the CLI, signing in is not enough

Cursor’s CLI keeps a per-directory approval list that is entirely separate from the browser sign-in you just completed, and it uses the word approval for both. So you authenticate successfully, the server shows as connected, all four tools are listed, and every call is refused.

In the folder you actually work in:

agent mcp enable astryke-hub
agent mcp list-tools astryke-hub

The second command confirms it. Move to a different folder and the approval does not follow you, so this is per project rather than once per machine.

Print mode refuses tool calls

Running the agent with -p enumerates the tools and then never calls any of them. We have not found a flag that changes this. If the tools are visible but nothing ever runs, use the interactive agent instead.

A warning about what it tells you

When Cursor could not call the tools, its agent explained that the desktop IDE was blocking them. That was not true, and nothing on our side had refused anything. An agent describing its own configuration is guessing, confidently, from the same documentation you have.

The reliable check is your board: open app.astryke.com and look at the Agents page. If Cursor connected, it is listed there with the time it was last heard from. That is a record of what actually reached the server, rather than an account of what an agent believes.

Still stuck? Troubleshooting, or every config format side by side.