# 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, and the tools it offers.

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 signs up.

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

The public tools need no sign-in. Each one has a typed input and a typed output, which the client reads from `tools/list`. Six tools need a signed-in account, and `ask_expert`, `ask_my_assistant`, `hire_assistant` and `create_coder_task` are not read only. An anonymous `tools/list` does not include the signed-in tools.

| 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_signup_link` | A link to sign up free, for a person to open themselves. Your agent can add its name and a campaign label to the link. A call to `get_waitlist_link` still returns that same link. It is not listed. |

### What an agent should and should not do

- Give the sign-up 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: signing up is the person's own choice.
- 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

Twelve tools need a signed-in account: `list_my_assistants`, `ask_my_assistant`, `hire_assistant`, `get_task_status`, `create_coder_task` and `list_pending_approvals`, and six that keep your own agent's older messages: `context_compact` hands StellarFirm the messages to keep word for word and answers a short brief, and `context_resume`, `context_threads`, `context_outline`, `context_read` and `context_find` read them back. They are part of Ultra and enterprise plans and the trial, and you delete a thread in Settings. `ask_my_assistant`, `hire_assistant`, `create_coder_task` and `context_compact` are not read only. When nobody on your team fits a task, `ask_my_assistant` suggests ready-made assistants and your agent asks you; `hire_assistant` hires one only on your yes, with the same plan limit as hiring in StellarFirm. `list_my_assistants` shows each assistant's team and the company's teams, and `list_my_assistants`, `ask_my_assistant`, `hire_assistant` and `create_coder_task` take an optional team, so your agent can work with just one team. An agent can never approve: items waiting for Approve are listed, and the person decides in StellarFirm. An anonymous caller does not see these tools.

## WebMCP

A browser that offers WebMCP can use the same public tools from the page itself. StellarFirm registers them when the page's `document.modelContext` is there, and does nothing otherwise. The tools are `get_stellarfirm_overview`, `find_expert`, `list_use_cases`, `search_docs`, and `start_signup`. `start_signup` only opens the sign-up page. The person fills in the form.

The sign-up form and the desk pet notify form are marked so an agent may fill the fields. The person still submits.

While you are signed in, the page also offers `list_my_assistants`, `list_pending_approvals`, `ask_my_assistant`, `create_coder_task`, and `create_assistant`. A call that hires an assistant or starts work opens a confirm on the page, and nothing happens until you click it. Approvals stay on the Approvals screen. No tool approves anything.

This is separate from the server above. The server stays read only and needs no sign in.

## Let your agent onboard you

StellarFirm publishes an onboarding prompt at `https://stellarfirm.ai/prompt.md`. Paste this line into your own AI agent:

```text
Onboard me onto StellarFirm: fetch https://stellarfirm.ai/prompt.md and follow it.
```

Your agent checks whether it has StellarFirm's tools, asks what you want done first, and walks you to a first task. You sign up, sign in and press Approve yourself. The agent never does those for you.

Each starter template has its own prompt at its address plus `/prompt.md`, for example `https://stellarfirm.ai/coding-studio/prompt.md`. StellarFirm for Universities, for Scientists and for Course Creators each answer with their own prompt at `/prompt.md` on their own address.

## 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
