docs

MCP

Connect your coding agent to Noonmark to read feedback from your existing workflow.

Noonmark’s remote MCP server lets your coding agent read forms and submissions without copying feedback into a prompt. Use that context in your existing coding session. Your own tools remain where you plan and complete the work.

Connect your client

  1. Create a workspace token in Studio’s Settings → Tokens.
  2. Choose read-only access unless your workflow needs the supported write tools.
  3. Add Noonmark to your MCP client with the URL and bearer token below. The exact configuration location depends on your client.
Read-only MCP configuration
{
  "mcpServers": {
    "noonmark": {
      "type": "http",
      "url": "https://noonmark.dev/mcp/readonly",
      "headers": {
        "Authorization": "Bearer nmk_YOUR_WORKSPACE_TOKEN"
      }
    }
  }
}

Use https://noonmark.dev/mcp and a read and write token when you need write access. The token identifies the workspace; the endpoint URL is shared. Keep your token private and out of version control. Tokens are shown once and can be revoked in Studio.

ChatGPT, Claude and Gemini

Use a client that supports remote MCP and can send the bearer token in the configuration above. This token is different from a Form's public API key.

  • ChatGPT: custom MCP apps depend on your plan and workspace settings. Check the available authentication options: Noonmark's current remote endpoint requires a bearer token; it does not provide an OAuth sign-in flow.
  • Claude: use an MCP-capable Claude client that supports the configuration above, such as Claude Code. Check your client’s remote-server authentication settings.
  • Gemini CLI: supports MCP server configuration, use its httpUrl setting for the endpoint and headers for the bearer token. Other Gemini interfaces may offer different connection options.

For an assistant working in a browser tab, use WebMCP instead. Opening a Form's link works with the page tools only when the browser agent supports WebMCP.

Read tools

ToolWhat it provides
list_formsForms in your workspace.
get_formA form’s fields and configuration.
list_submissionsIncoming submissions, with search, pagination and status filters.
get_submissionA submission’s payload and associated context.
list_insightsThe counts the Studio’s Insights page shows.

Try asking your agent to list new bug reports, retrieve a specific report or summarise what users sent. The agent’s answer depends on your actual submissions.

Write tools

A read and write token at /mcp also enables:

  • submit_submission: send a payload to a form, subject to its field validation.
  • set_submission_status: update a submission’s status with an optional note.
  • create_form: create a form in your workspace.
  • set_submission_check: tick or untick a named check on a submission.
  • retry_gate: run the Gate again on one submission. It uses the workspace’s OpenAI key when one is set.
  • redeliver_webhook: send a logged webhook delivery again.

These tools operate on Noonmark data. Creating a ticket in another tool or changing your app requires your own integration or your agent’s other tools. There is no MCP deletion tool.

Other ways to connect

Use signed webhooks to deliver events to your own endpoint. WebMCP is a separate browser capability for interacting with survey pages and signed-in Studio tabs.

What did you think of this content?

On this page