/connect

Connect your agent

One MCP server plus installable skills. The same server serves public Atlas tools and authenticated hosted MFM Spec tools; the skills teach your agent how to use them.

$ agent prompt

Give this to an agent that can configure its own MCP servers:

Set up the MadeForMachine MCP connector for this agent.

Use server name: mfm
Use endpoint: https://mcp.mfm.dev/mcp

Configure the server using this harness's native MCP setup mechanism. Complete OAuth if the server asks for it. Verify that public Atlas tools are visible, and if the account is authenticated for MFM Spec, verify that the mfm_spec_* tools are visible too. If tools were just authorized but are not visible in this running session, start a fresh agent session or reload the MCP/tool registry before claiming setup is done.

$ manual setup

general

Server name: mfm
Transport: Streamable HTTP
URL: https://mcp.mfm.dev/mcp
Auth: OAuth for tenant-scoped tools

Expected behavior:
- Anonymous sessions can see public Atlas read tools.
- Authenticated sessions can see mfm_spec_* tools.
- Operator sessions can see Atlas construction tools.

Claude Code

claude mcp add --transport http mfm https://mcp.mfm.dev/mcp
claude mcp login mfm
claude mcp list

Codex

codex mcp add mfm --url https://mcp.mfm.dev/mcp
codex mcp login mfm
codex mcp list

Cursor

// ~/.cursor/mcp.json for global setup
// .cursor/mcp.json for project setup
{
  "mcpServers": {
    "mfm": {
      "url": "https://mcp.mfm.dev/mcp"
    }
  }
}

Then open Cursor MCP settings and authenticate the mfm server.

$ verify

If mfm_spec_* tools are missing, check auth first. In OAuth mode gated tools are hidden from tools/list when the session is unauthenticated.

If login just succeeded but tools are still missing, start a fresh agent session so the tool list is rebuilt.

If public Atlas tools are also missing, the MCP server is not connected or the endpoint is wrong.

If a direct API call returns 401, the MCP session token is missing, expired, or not being forwarded.

$ skills

Public skills that teach your agent how to use MFM services. Humans can inspect what a skill does; agents read the same generated manifest from /skills.json.

Atlas Skillbeta · v0.1.0slug: atlas · connector: mfm · 5 tools

Use when choosing, comparing, or integrating a third-party service, API, or SDK (auth, payments, email, storage, etc.). Query MadeForMachine Atlas — an intelligence engine for product and feature discovery and comparison — over MCP, jumping straight to the doc evidence for a capability instead of crawling a provider's docs or recalling from stale training data.

MFM Spec hosted skillalpha · v0.3.0slug: mfm-spec · connector: mfm · 11 tools

Use when working with hosted MFM Spec: a spec stored in the MadeForMachine service and read, mutated, validated, and versioned through MCP tools. Use for service-backed spec authoring, minimal-context reads, fine-grained spec mutations, validation, history, and evaluation notes. Do not use for local file-backed specs; use the mfm-spec-local skill for that.

MFM Spec local skillmvp · v0.7.0slug: mfm-spec-local · no connector · 0 tools

Use when turning rough software intent into a valid local MFM Spec: components, features, evaluations, decisions, and validation-ready project memory.