MCP Server

Connect UnifiedModels to your AI assistant or coding agent. Through the Model Context Protocol (MCP), tools like Claude, ChatGPT, Cursor, VS Code and Codex can read and edit your data models, generate code in 30 languages and schema formats, import existing schemas, and push the results to GitHub.

Quick start

Use this URL wherever your client asks for a remote MCP server:

https://api.unifiedmodels.com/mcp

1. Add the URL above to your client. Pick your client in Connect your client.
2. Your client opens a browser window. Sign in to UnifiedModels (or sign up) and approve the permissions it asks for.
3. Ask your assistant something like “List my UnifiedModels projects.”

There is no API key to copy or rotate: your client stores and refreshes its sign-in for you.

What you can do

• Browse your work: list every project you own or collaborate on and read its models, enums, constants, target languages and connected repositories.
• Edit models, enums and constants: create, update, rename and delete them one at a time, or change a single field. Renaming updates every reference; deleting clears references and tells you what changed.
• Manage projects: create a project, replace one wholesale, or delete it (owners and project admins only).
• Generate code: render a project in any of the 30 supported languages and schema formats below.
• Import schemas: paste a schema or source file in any of 18 formats; the assistant can detect the format, parse it into models and enums, and save the ones you want.
• Push to GitHub: list the repositories and branches of the GitHub account connected to UnifiedModels, and commit generated code to a project's connected repositories.

Supported languages and formats

Language ids are what the tools take; your assistant can also look them up with list_languages.

Connect your client

Any client that supports remote MCP servers with OAuth can connect directly. Instructions for popular clients follow; menus move between releases, so check your client's own MCP documentation if a step does not match.

claude mcp add --transport http unifiedmodels https://api.unifiedmodels.com/mcp

codex mcp add unifiedmodels --url https://api.unifiedmodels.com/mcp
codex mcp login unifiedmodels

[mcp_servers.unifiedmodels]
url = "https://api.unifiedmodels.com/mcp"

{
  "mcpServers": {
    "unifiedmodels": {
      "url": "https://api.unifiedmodels.com/mcp"
    }
  }
}

code --add-mcp '{"name":"unifiedmodels","type":"http","url":"https://api.unifiedmodels.com/mcp"}'

{
  "servers": {
    "unifiedmodels": {
      "type": "http",
      "url": "https://api.unifiedmodels.com/mcp"
    }
  }
}

{
  "mcpServers": {
    "unifiedmodels": {
      "serverUrl": "https://api.unifiedmodels.com/mcp"
    }
  }
}

gemini mcp add --transport http unifiedmodels https://api.unifiedmodels.com/mcp

{
  "mcpServers": {
    "unifiedmodels": {
      "httpUrl": "https://api.unifiedmodels.com/mcp"
    }
  }
}

{
  "context_servers": {
    "unifiedmodels": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.unifiedmodels.com/mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "unifiedmodels": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.unifiedmodels.com/mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "unifiedmodels": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.unifiedmodels.com/mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "unifiedmodels": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.unifiedmodels.com/mcp"
      ]
    }
  }
}

Permissions

When you approve a client, the consent screen lists the scopes it is asking for. Each tool checks for the scope it needs, so you can, for example, give a client read-only access to your projects.

Tools

Tools that address a single model, enum or constant accept either its id or its name. Prefer upsert_model, upsert_enum and upsert_constant over upsert_project: they change only that one item, so they cannot overwrite someone else's concurrent edit.

Resources

Clients that support MCP resources can also attach these read-only views as context:

Example prompts

• “List my UnifiedModels projects and show me the models in the Billing project.”
• “Add an optional phone string field to the Customer model.”
• “Rename the Status enum to OrderStatus.”
• “Here's our OpenAPI spec. Import its schemas into my Orders project.”
• “Generate the Orders project as Zod and as Prisma.”
• “Push the Orders project to its connected GitHub repo.”

Good to know

• generate_code returns at most 100,000 characters, so it does not flood your assistant's context. For the full output, read the unifiedmodels://project/{project_id}/generate/{language} resource.
• parse_schema only parses; nothing is saved until the assistant upserts the results.
• The GitHub tools use the GitHub account connected to your UnifiedModels user, and push_to_repo pushes to the repositories connected to the project. Set both up in the web app first.
• push_to_repo makes real commits, and the delete tools are permanent. Most clients ask before running tools that change data; keep that confirmation on.

Security and revoking access

• The MCP server acts only as the account you signed in with, only on projects that account owns or collaborates on, and only within the scopes you approved.
• Access tokens last one hour and only work with this server. Refresh tokens last 30 days and are replaced every time they are used; if an old one is ever reused, every token descended from it is revoked.
• Every sign-in uses PKCE (S256), so a stolen authorization code cannot be redeemed.
• To stop a client using your account, disconnect or remove UnifiedModels in that client. To revoke access on our side, contact us.

See our Privacy Policy for how your data is handled.

Troubleshooting

For client developers

• Transport: Streamable HTTP, POST only. The server is stateless and serves protocol revision 2026-07-28 (no initialize handshake) as well as earlier revisions back to 2025-03-26. There is no GET stream and no legacy HTTP+SSE endpoint.
• Protected resource metadata (RFC 9728): https://api.unifiedmodels.com/.well-known/oauth-protected-resource/mcp
• Authorization server metadata (RFC 8414): https://api.unifiedmodels.com/.well-known/oauth-authorization-server
• Clients can identify themselves with a Client ID Metadata Document (an HTTPS URL as the client_id) or register through Dynamic Client Registration at https://api.unifiedmodels.com/oauth/register.
• Grants: authorization_code with PKCE S256 (plain is refused) and refresh_token. Public clients and client_secret_post / client_secret_basic are supported, and authorization responses carry iss (RFC 9207).
• Access tokens are audience-bound to https://api.unifiedmodels.com/mcp. A 401 response carries a WWW-Authenticate challenge naming the resource metadata and every scope the tools use.

Need help?

If you have trouble connecting, contact us.