https://mcp.usenotra.com/mcp (streamable HTTP) so AI agents can work with your workspace. Connected agents can manage brand identities, generate, edit, schedule and publish content, preview and publish posts on Notra Sites, follow their builds and manage their authors, connect integrations and manage schedules, event triggers, webhooks and skills. They can also use every GEO feature: projects, prompts, competitors, scans, visibility, content briefs, agent readiness, AI traffic and website analytics.
This page covers two things:
- Notra’s MCP server. Give an AI client (Claude, Cursor, ChatGPT, Codex and others) access to Notra.
- External MCP servers. Give Notra’s chat agent access to your own tools by connecting servers under Integrations > MCP Servers.
Authentication
The server accepts bearer credentials in theAuthorization header, either as an OAuth access token or as a Notra API key.
- OAuth (recommended for interactive clients)
- API key (headless and CI)
Use OAuth when a person is present, for example in Claude, Cursor, ChatGPT connectors and any client that supports OAuth discovery. You add the server URL and the client opens a browser. After you sign in to Notra and pick an organization, the client stores the token.Clients discover everything from the protected resource metadata:That document lists the authorization server (Permissions like
https://oauth.usenotra.com), the supported scopes and the bearer method. The authorization server supports dynamic client registration, client ID metadata documents, the authorization code flow with PKCE and refresh tokens. The API mirrors the same metadata at https://api.usenotra.com/.well-known/oauth-protected-resource and https://api.usenotra.com/.well-known/oauth-authorization-server.Request these two scopes and nothing else:posts.read or projects.write are not OAuth scopes, so requesting them fails with invalid_scope. Instead, you pick the organization and an access level (Read only, Write only or Full access) on the consent screen. Notra signs that choice into the access token and maps it to the same permissions API keys use, so the session acts as you, in that organization, with that access level.Access tokens are short-lived, so clients should include
offline_access in the requested scope to receive a refresh token. Without it, the connection drops when the access token expires and you have to sign in again.Connect an AI client
With OAuth
Add the server URL without any headers, and the client detects the OAuth metadata and opens the sign-in flow.https://mcp.usenotra.com/mcp as a custom connector in either app and complete the sign-in when prompted.
With an API key
If your client supportsadd-mcp, install the server with a header override:
Local stdio server
The same server is published on npm as@usenotra/mcp for clients that only speak stdio. It needs Node.js 20 or newer and an API key in NOTRA_API_KEY:
Load only the tools you need
The server exposes every tool by default. Many clients load all tool definitions into the agent’s context up front, so if you only use part of Notra, pick a toolset to keep that context small:
Workspace tools and
submit_feedback are always available. Add the toolsets query parameter to the hosted URL, or set NOTRA_MCP_TOOLSETS for the npm package. Separate several toolsets with commas.
notra to Claude Code, run claude mcp remove notra first, because claude mcp add does not replace an existing server with the same name. In Cursor, edit the existing entry.
The server rejects an unknown toolset name with an error instead of silently hiding tools. OAuth sign-in works the same with the query parameter.
Available tools
Tool names match exactly what the server registers, although some clients prefix them with the server name. Workspacewhoamilist_workspaces(only on connections that can reach several workspaces)
list_postsget_postcreate_postupdate_postdelete_postgenerate_postget_post_generation_statuscreate_post_pull_requestget_post_scheduleschedule_postcancel_post_schedule
update_post changes the title, slug or markdown of a blog post or changelog with a linked GitHub pull request, Notra saves the article and updates that PR using the same publishing logic as the dashboard, without creating a new PR. Status-only changes do not trigger a GitHub update.
If the PR update fails, the tool returns an error stating that Notra saved the post. A rate-limited GitHub sync returns 429 with Retry-After, so wait before retrying the content update. A timeout returns 504 with an unknown sync outcome, and because the PR update may still finish, check the PR before retrying, as you should after any other unconfirmed sync error. If the PR is closed or merged, resolve it in the dashboard before Notra can sync it again.
To turn a pull request into a post, call generate_post with pullRequest and, if you like, a brief in your own words. Poll get_post_generation_status until it reports a postId, then call create_post_pull_request to open a draft pull request with the post. Calling it again updates that pull request.
Sites
list_sitesget_sitelist_site_deploymentsget_site_deploymentdeploy_siteredeploy_site_deploymentpreview_post_on_siteget_site_post_previewpublish_post_to_site
publish_post_to_site always opens or updates a pull request, even when the repository publishes directly from the dashboard, so the post goes live only after someone merges it. get_site_deployment returns compiler diagnostics and the newest build log output. Domains, settings, rollbacks and deletion stay in the dashboard.
Sites authors
list_site_authorsupsert_site_authordelete_site_authorimport_site_authorsset_site_author_pagepublish_site_design
blog.json as unpublished Design changes, the same ones the dashboard’s Design tab shows, and go live when publish_site_design or the dashboard publishes them. publish_site_design refuses while other files on the site have unpublished changes, so work you staged in the dashboard is never published by accident. To credit a site author on a blog post that publishes to the site, pass its site:<id> ref in authorIds of update_post.
The Sites tools need the sites.read and sites.write scopes.
Brand identities
list_brand_identitiesget_brand_identityupdate_brand_identitydelete_brand_identitygenerate_brand_identityget_brand_identity_generation_statuslist_brand_colorscreate_brand_colorupdate_brand_colordelete_brand_color
list_integrationslist_github_activitycreate_github_integrationdelete_integration
list_schedulescreate_scheduleupdate_scheduledelete_schedulerun_schedulelist_schedule_runslist_event_triggersget_event_triggercreate_event_triggerupdate_event_triggerdelete_event_trigger
list_webhook_endpointsdelete_webhook_endpointlist_webhook_deliveriesget_webhook_deliveryretry_webhook_delivery
list_skillsget_skillcreate_skillupdate_skilldelete_skill
list_projectsget_projectcreate_projectupdate_projectdelete_projectget_geo_settingslist_geo_enginesupdate_geo_settings
get_geo_snapshotget_geo_changesget_geo_prompt_historyget_geo_sentimentget_geo_sentiment_analysislist_geo_sentiment_evidencelist_geo_shelf_sources
get_geo_snapshot. It returns a compact diagnosis of a project and the recommended next actions.
GEO prompts and sequences
list_geo_promptscreate_geo_promptupdate_geo_promptdelete_geo_promptimport_geo_promptslist_geo_prompt_suggestionsaccept_geo_prompt_suggestiondismiss_geo_prompt_suggestionlist_geo_sequencescreate_geo_sequenceupdate_geo_sequencedelete_geo_sequencerun_geo_sequence
list_geo_competitorsupsert_geo_competitorsuggest_geo_competitorsdelete_geo_competitorimport_geo_competitors
create_geo_scanrescan_geo_promptlist_geo_scansget_geo_scanget_geo_visibility_overviewget_geo_visibility_timeserieslist_geo_prompt_result_summariesget_geo_prompt_result_detailget_geo_competitor_shareget_geo_language_shareget_geo_competitor_detail
list_geo_content_gapsupdate_geo_content_gaplist_geo_content_briefsplan_geo_content_briefget_geo_content_briefupdate_geo_content_briefapprove_geo_content_brief
get_geo_agent_readinessstart_geo_agent_readiness_scan
get_geo_traffic_overviewget_geo_traffic_loglist_geo_traffic_journeysget_geo_traffic_journeylist_geo_traffic_pagesget_geo_traffic_journey_statsget_geo_ingest_setup(includes the public notra.js web key and pinned script URLs)
get_geo_web_analyticsget_geo_web_analytics_breakdownslist_geo_analytics_imports
get_geo_web_analytics returns views, visitors, sessions and AI-referred visitors against the previous period, and get_geo_web_analytics_breakdowns returns pages, sources, countries, devices, languages, outbound links, Core Web Vitals and JavaScript errors. History imports need provider credentials, so start them in the dashboard; the MCP server only reports their progress.
MCP server analytics
get_geo_mcp_analyticssummarizes how agents use your own MCP server: tool calls, errors, latency, clients, models and tools nobody calls.get_geo_mcp_tool_analyticsshows one tool’s failures and which tools agents call right before and after it.
@usenotra/sdk/mcp. Captured arguments, responses and end-user IDs stay in the dashboard.
Feedback
list_feedback,get_feedbackandupdate_feedbackwork with the feedback your own users send you.submit_feedbacksends a bug report, feature request, question or praise to the Notra team and needs no credentials. See Agent feedback.
Connect external MCP servers to Notra
Notra’s chat agent can also use tools from MCP servers you run or subscribe to. Open Integrations > MCP Servers in the dashboard (or pressC on that page) and add a server.
1
Describe the server
Give it a name, the server URL (for example
mcp.example.com/mcp) and a short description of what tools or context Notra should use it for. The agent uses the description to decide when to use the server.2
Choose authentication
Pick one of three options:
- None for public servers without credentials.
- API key to send one or more custom headers, such as
Authorization: Bearer .... - OAuth to sign in with the server’s own OAuth flow, which Notra opens in a popup.
3
Test and save
Notra tests the connection before saving and reports whether it could reach the server. With OAuth, the button reads Connect & Authorize and Notra saves the server once authorization completes.
Composio
If you want to use the Notra MCP server through Composio, upvote the request at request.composio.dev/boards/tool-requests/posts/notra so the Composio team sees demand for a Notra integration.Notes
- Prefer OAuth for personal clients so tokens rotate and can be revoked per session.
- Keep API keys in a server-side or local secret store, and do not commit MCP config files that contain live bearer tokens.
- Revoke and replace a key immediately if it is exposed.

