Noma

Integration hub · Last reviewed April 2026

AI coding agents

Pair Noma with your favorite agent

Noma’s MCP server exposes collections, fields, entries, assets, and webhooks as tools. Any agent that can run a stdio MCP server—or wrap the same command—can manage content alongside your code.

More agents

The integration pattern is always the same: run npx -y @nomacms/mcp-server with NOMA_API_KEY and NOMA_PROJECT_ID. Drop that command into whatever configuration surface your product exposes for MCP or “external tools.”

  • GitHub Copilot

    When your Copilot build exposes MCP (for example via workspace or agent configuration), point it at the same stdio command: npx -y @nomacms/mcp-server with NOMA_API_KEY and NOMA_PROJECT_ID.

  • Google Antigravity

    Use the product’s MCP configuration surface (often JSON alongside other agent settings) and register a stdio server with the identical npx invocation and environment variables.

  • VS Code–based agents

    Any extension that supports MCP over stdio can launch the npm package; prefer env interpolation so API keys never land in source control.

  • JetBrains AI Assistant / Junie

    If MCP or external tool bridges are available in your edition, reuse the same command and env pattern. Fall back to manual REST calls via @nomacms/js-sdk when MCP is not exposed.

  • Windsurf & other forks

    Follow the host’s documented MCP JSON format; structurally it mirrors Cursor’s mcpServers entries.

Source reference: github.com/NomaCMS/nomacms-mcp-server · Agent skills on GitHub

Now available

Start building with Noma

Create a free account, spin up a project, and ship structured content with our API, SDK, and AI tools.