Hosted MCP server

Give your coding agent your specs.

One URL connects Claude Code, Claude Desktop, Cursor or Codex to your CodeMySpec project: its stories, acceptance criteria, components and requirements.

https://codemyspec.com/mcp/harness

Your client opens a browser to sign in the first time. There is no API key to paste.

add it to your client

Pick your client.

Add the server, then start Claude Code and ask it for a story. The first tool call opens the sign-in.

Terminal
claude mcp add --transport http codemyspec https://codemyspec.com/mcp/harness
or, for the whole build loop

The plugin brings the same server plus the hooks that run tests and BDD specs on your machine. Those need the local cms server: install it first.

In Claude Code
/plugin marketplace add Code-My-Spec/plugins\n/plugin install codemyspec@codemyspec

No config file. Open Settings, then Customize, click Add connector, paste the server URL, and sign in when the browser window opens.

https://codemyspec.com/mcp/harness

Add this to ~/.cursor/mcp.json (every project) or .cursor/mcp.json (this project), restart Cursor, and check Settings, then MCP, for the server.

~/.cursor/mcp.json
{
  "mcpServers": {
    "codemyspec": {
      "url": "https://codemyspec.com/mcp/harness"
    }
  }
}

The Codex plugin carries the server. Codex support is early.

Terminal
codex plugin marketplace add Code-My-Spec/plugins

Then install codemyspec from /plugins and enable its hooks from /hooks. Latest steps are in the plugin repo.

Any MCP client that speaks Streamable HTTP and OAuth can connect. Give it these:

Server details
URL:       https://codemyspec.com/mcp/harness
Transport: Streamable HTTP
Auth:      OAuth 2.0 with PKCE, dynamic client registration

Your client finds the sign-in from the server's /.well-known/oauth-protected-resource answer and registers itself.

keys and storage

What it needs and what it keeps.

  • Sign-in: OAuth in your browser with a CodeMySpec account. Your client keeps the token.
  • Stored with us: your account and the project records the tools read and write: stories, acceptance criteria, components, requirements and issues.
  • Which project: calls go to your active project. Pick it once on codemyspec.com.
  • On your machine: nothing new to connect. Writing code, running tests and BDD specs happen locally, through the cms server and plugin.

what you get

What your agent can do once it is connected.

01

Write stories

Interview you about a feature and write the user stories, then review them for gaps.

02

Agree the criteria

Run a Three Amigos session to turn a story into acceptance criteria your BDD specs test.

03

Know what is next

Read your components and requirements, and ask get_next_requirement for the next piece of work.

The tool list stays short on purpose: a few direct tools, and the rest through tool_docs and run_script. You ask in plain language; your client does the calling.