# StellarFirm MCP server

> Connect an AI agent or coding tool to the public StellarFirm MCP server: the address, install steps for Cursor, Claude and VS Code (with a one-click Add to Claude link), and its read only tools.

StellarFirm runs a public MCP server. MCP, the Model Context Protocol, is the open standard that lets an AI agent or a coding tool call tools on another service. Connect it and your agent can answer questions about StellarFirm from the source: what it is, which use cases it covers, what the docs say, and how a person joins the waitlist.

The server is read only and needs no sign in. It cannot sign anyone up, send anything, or approve anything. Approve stays with the person.

## The address

| What | Value |
| --- | --- |
| Endpoint | `https://stellarfirm.ai/mcp` |
| Alias | `https://stellarfirm.ai/api/mcp` |
| Transport | Streamable HTTP, a single POST for each message |
| Sign in | None |
| Server card | `https://stellarfirm.ai/mcp/server-card` |
| Manifest | `https://stellarfirm.ai/.well-known/mcp.json` |

## Install

### Cursor

Add this to `~/.cursor/mcp.json`, or to `.cursor/mcp.json` in a project:

```text
{
  "mcpServers": {
    "stellarfirm": {
      "url": "https://stellarfirm.ai/mcp"
    }
  }
}
```

### Claude Code

```text
claude mcp add --transport http stellarfirm https://stellarfirm.ai/mcp
```

### Claude

[Add StellarFirm to Claude](https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=StellarFirm&connectorUrl=https%3A%2F%2Fstellarfirm.ai%2Fmcp%3Fvia%3Ddocs) opens Claude's **Add custom connector** dialog with the name and address filled in. Check them and confirm; the link adds nothing by itself.

### Claude Desktop

Open **Settings**, then **Connectors**, choose **Add custom connector**, and paste `https://stellarfirm.ai/mcp`. If your version only reads a config file, bridge the address with `mcp-remote` in `claude_desktop_config.json`:

```text
{
  "mcpServers": {
    "stellarfirm": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://stellarfirm.ai/mcp"]
    }
  }
}
```

### VS Code

Add this to `.vscode/mcp.json` in a project, or run **MCP: Add Server** from the command palette and choose **HTTP**:

```text
{
  "servers": {
    "stellarfirm": {
      "type": "http",
      "url": "https://stellarfirm.ai/mcp"
    }
  }
}
```

### Any other client

Any client that speaks Streamable HTTP works with the endpoint above. You can also call it by hand:

```text
curl -s https://stellarfirm.ai/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
```

## Tools

Every tool is read only, changes nothing, and gives the same answer to the same question. Each one has a typed input and a typed output, which the client reads from `tools/list`.

| Tool | What it does |
| --- | --- |
| `get_stellarfirm_overview` | What StellarFirm is, which assistants it offers, how access works, and who it suits and who it does not. |
| `find_expert` | The ready-made assistants that fit a problem in the person's words, such as tutoring calculus with hints or fitting peaks in particle physics data, with what each does and good first tasks. It hands no task over. |
| `list_use_cases` | The starters, with an optional filter by industry. |
| `get_use_case` | One starter by its id: the pitch, the team, the integrations, and links. |
| `search_docs` | Searches these docs and returns matching pages with a short excerpt and a link. |
| `get_waitlist_link` | A link to the waitlist for a person to open and join themselves. Your agent can add its name and a campaign label to the link. |

### What an agent should and should not do

- Give the waitlist link to the person and let them decide. The server has no tool that signs anyone up or sends their email address anywhere, on purpose: joining needs the person's own consent.
- Tell the person that every assistant is available on StellarFirm web today.
- Never claim that an agent can approve work for a person. Anything that sends, deploys, publishes or charges waits for the person's Approve.

## When a call fails

A failed tool call comes back as a normal result with `isError` set, so the model can read it and try again. A protocol failure comes back as a JSON-RPC error. Both carry the same structured details:

| Field | Meaning |
| --- | --- |
| `code` | The JSON-RPC code. |
| `message` | What went wrong. |
| `type` | A stable name to branch on, such as `invalid_arguments`, `not_found`, `unknown_tool` or `rate_limited`. |
| `hint` | What to do next. |
| `retryAfterSeconds` | How long to wait, when the server asked you to slow down. |

One address can make a limited number of calls in a minute. Past that the server answers with status 429 and a `Retry-After` header.

## Signed in tools

Tools that act for one person, such as listing their assistants, checking a task, or giving the Coder a task, are not offered yet. They need a signed in connection that the person grants, and they will stay behind a switch until it exists. When they arrive, an agent will be able to look and to hand a task to the Coder. It will not be able to approve: items waiting for Approve are listed, and the person decides in StellarFirm.

## Next

- [What is StellarFirm?](/docs/getting-started/what-is-stellarfirm): the idea in plain words.
- [Approvals](/docs/ceo/approvals): how Approve keeps you in control.
- Questions or a missing tool? Write to hey@stellarfirm.ai.

---

Source: https://stellarfirm.ai/docs/getting-started/mcp-server