MCP Server

Connect AI assistants like Claude Code and Claude Desktop directly to your Notedis feedback. The Notedis MCP server uses the Model Context Protocol — an open standard for connecting AI tools to external services — so your assistant can list your sites, browse tickets, reply to submitters, and close resolved conversations for you.

Pro feature: The MCP server is available on the Pro Monthly and Pro Annual plans. See pricing to upgrade.

What You Can Do

Once connected, your AI assistant can work with your feedback directly:

  • Triage your inbox - "Summarize my open tickets and tell me which ones look urgent"
  • Investigate bugs - "Pull up ticket #A1B2C3 and the browser info the submitter's screenshot captured"
  • Respond to clients - "Draft and send a reply letting them know the fix is deployed"
  • Close the loop - "Close every ticket about the checkout bug we fixed today"

Replies sent through MCP are posted as you, and the ticket submitter is notified by email — exactly as if you replied from the dashboard.

Connecting

Step 1: Create an API Token

  1. Go to API Tokens in your account menu
  2. Give the token a name (e.g. "Claude Code")
  3. Choose the permissions the token should have (see Token Permissions below)
  4. Click Create and copy the token — it's only shown once

Step 2: Add the Server to Your Assistant

The server lives at:

https://notedis.com/mcp

It uses the streamable HTTP transport with bearer token authentication.

Claude Code (one command):

claude mcp add --transport http notedis https://notedis.com/mcp \
  --header "Authorization: Bearer YOUR_API_TOKEN"

Claude Desktop / other MCP clients:

Add the server to your client's MCP configuration:

{
  "mcpServers": {
    "notedis": {
      "type": "http",
      "url": "https://notedis.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}

Step 3: Try It

Ask your assistant something like "List my Notedis sites" — it should call the list-sites tool and show your sites.

Available Tools

Tool Description Required Permission
list-sites List the sites you can access read
list-feedback Browse a site's tickets with status, search, and pagination filters read
get-feedback Get a ticket's full details and conversation thread read
reply-to-feedback Post a reply to a ticket (emailed to the submitter) create
update-feedback-status Open or close a ticket update

Ticket IDs used by the tools are the same public IDs shown in the web app as [Ticket #...].

Token Permissions

Token permissions let you control exactly what an assistant can do:

  • read - View sites and tickets. Safe for read-only workflows like summaries and triage.
  • create - Post replies to tickets. Replies are sent as you and emailed to the submitter.
  • update - Change ticket status. Closing a ticket notifies the submitter that the conversation is resolved.

New tokens default to read only. For a fully autonomous assistant, grant all three. You can change a token's permissions at any time from the API Tokens page.

Site Access

The MCP server sees the same sites you do:

  • Sites you own
  • Sites you've been granted access to
  • Sites in workspaces where you're an owner or manager

Guests can connect too — they'll only see the tickets they submitted themselves.

Security

  • Treat tokens like passwords. Anyone with your token can act on your feedback as you.
  • Scope tokens tightly. Use a read-only token unless you need the assistant to reply or close tickets.
  • Revoke freely. Delete a token at any time from the API Tokens page and the connection stops working immediately.
  • Rate limited. Requests are limited to 60 per minute per account.

Troubleshooting

"401 Unauthorized"

Your token is missing, mistyped, or has been deleted. Create a new token and update your client's Authorization header.

"MCP access requires a Pro plan"

The MCP server is a Pro feature. Upgrade on the pricing page, or check that your subscription is still active.

The assistant can't see a site

Confirm you can see the site in the dashboard. MCP access mirrors your account's site access — if it's missing there, ask the site owner to invite you.

A tool call fails with a permission error

The token is missing the required permission (create for replies, update for status changes). Edit the token's permissions on the API Tokens page.

Need Help?

Email us at [email protected] — we're happy to help you get connected.

TeamTroubleshooting