Skip to main content
Glama
notra

notra

Official
by usenotra

Notra MCP Server

An MCP (Model Context Protocol) server for the Notra API. It manages posts, brand identities, integrations, schedules, GEO visibility scans, competitors, content briefs, and AI traffic analytics.

Install from a directory

The quickest way to connect is a one-click listing, which signs you in with OAuth:

Opening https://mcp.usenotra.com/mcp in a browser shows setup steps for Claude Code, Cursor, VS Code and ChatGPT. Machine-readable discovery is published as an MCP Server Card and an AI catalog.

Related MCP server: Novu MCP Server

Interactive charts

GEO and traffic tools render as interactive MCP Apps views in clients that support them (ChatGPT, Claude and other MCP Apps hosts), and return the same data as JSON everywhere else. The charts follow the Notra dashboard's look and the host's light or dark theme. Coding agents are left out of the engine charts:

Tool

View

get_geo_visibility_timeseries

Mentions per day, overall and per engine

get_geo_visibility_overview

Mention rate per engine

get_geo_competitor_share

Share of voice donut, plus brand trends with includeTrends

get_geo_competitor_detail

Daily mentions and recent prompts for one brand

get_geo_sentiment

Sentiment score, daily positive/neutral/negative mix, per-engine split

get_geo_language_share

Mention rate per prompt language

get_geo_traffic_overview

AI crawler, citation, referral and conversion funnel with daily trend

get_geo_web_analytics

Visitors, views, sessions and AI visitors

get_geo_traffic_journey_stats

AI journeys per day and top pages

get_geo_mcp_analytics

MCP requests per day, latency and top tools

get_geo_persona_activity

Mention rate per persona over time

get_geo_agent_readiness

Readiness score gauge, history and open issues

get_post_agent_reach

AI traffic to one published post

Views live in views/ and are built with mcp-use into build/views.json, so they ship with both the npm package and the hosted server. Cards and tables come from the Notra UI registry; pnpm sync:ui refreshes them in views/components.

Setup

You can generate an API key from your Notra workspace dashboard under Developer > API Keys.

Node.js 20 or newer is required. Node 24 is recommended.

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "notra": {
      "command": "npx",
      "args": ["-y", "@usenotra/mcp"],
      "env": {
        "NOTRA_API_KEY": "your-api-key"
      }
    }
  }
}

Claude Code

claude mcp add notra -- npx -y @usenotra/mcp

Then set the NOTRA_API_KEY environment variable in your shell before launching Claude Code.

Codex

export NOTRA_API_KEY=your-api-key
codex mcp add notra --env NOTRA_API_KEY="$NOTRA_API_KEY" -- npx -y @usenotra/mcp

Run codex mcp list to verify the connection. The Codex CLI, desktop app, and IDE extension share this MCP configuration.

OpenCode

Set NOTRA_API_KEY in your shell, then add the server to your project-level opencode.json or the global ~/.config/opencode/opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "notra": {
      "type": "local",
      "command": ["npx", "-y", "@usenotra/mcp"],
      "enabled": true,
      "environment": {
        "NOTRA_API_KEY": "{env:NOTRA_API_KEY}"
      }
    }
  }
}

Amp

Run amp config edit and add the following to your settings, or place it in .amp/settings.json for a workspace-specific configuration:

{
  "amp.mcpServers": {
    "notra": {
      "command": "npx",
      "args": ["-y", "@usenotra/mcp"],
      "env": {
        "NOTRA_API_KEY": "${NOTRA_API_KEY}"
      }
    }
  }
}

Set NOTRA_API_KEY in the environment before launching Amp. Workspace MCP servers may require approval with amp mcp approve notra.

Account API keys

An account API key belongs to you rather than one workspace, so it works in every workspace you're a member of. If you belong to more than one, choose the workspace this server acts on with NOTRA_ORGANIZATION_ID:

{
  "env": {
    "NOTRA_API_KEY": "your-account-api-key",
    "NOTRA_ORGANIZATION_ID": "your-workspace-id"
  }
}

Without it, tools fail with a message asking you to pick a workspace. list_workspaces works without a selection and shows the ids. Organization API keys ignore NOTRA_ORGANIZATION_ID.

Remote MCP (OAuth)

The hosted streamable HTTP server at https://mcp.usenotra.com/mcp uses OAuth as the primary authentication method. It is built on mcp-use and supports the current 2026-07-28 MCP protocol as well as legacy 2025 clients, which are served statelessly without sessions. MCP clients should discover protected resource metadata at:

https://mcp.usenotra.com/.well-known/oauth-protected-resource/mcp

That metadata points to the Notra authorization server (WorkOS AuthKit) at https://oauth.usenotra.com, which supports dynamic client registration (RFC 7591). The MCP server also mirrors the authorization server metadata at https://mcp.usenotra.com/.well-known/oauth-authorization-server.

Workspace-scoped URL

Add a workspace id or slug to the URL to pin a connection to one workspace: https://mcp.usenotra.com/mcp/<workspace>. This is the way to pick a workspace in clients that only accept a URL and can't send custom headers.

  • Claude: Settings > Connectors > Add custom connector, URL https://mcp.usenotra.com/mcp/acme

  • Claude Code: claude mcp add --transport http notra https://mcp.usenotra.com/mcp/acme

  • Cursor (~/.cursor/mcp.json):

    {
      "mcpServers": {
        "notra": { "url": "https://mcp.usenotra.com/mcp/acme" }
      }
    }

On a scoped URL:

  • API keys act in that workspace. The URL wins over an X-Notra-Organization-Id header. An organization key only works on its own workspace's URL; any other workspace is rejected with HTTP 403 by the Notra API.

  • OAuth works the same as on /mcp, but the workspace you authorize must be the one in the URL. Otherwise requests are rejected with HTTP 403 instead of silently acting on another workspace. The OAuth challenge announces the same resource as /mcp, so clients get a normal Notra token; the workspace in the URL is enforced through the workspace you authorize.

  • list_workspaces is hidden, since the connection can't switch workspaces. whoami still shows the current one.

API key alternative

Remote connections also accept a Notra API key as a static Authorization: Bearer … header. Generate one from your Notra workspace dashboard under Developer > API Keys. OAuth-capable clients should prefer the OAuth flow instead of manual key configuration.

With an account API key that can reach several workspaces, use a workspace-scoped URL or add an X-Notra-Organization-Id: <workspace-id-or-slug> header (X-Organization-Id also works). The server forwards it to the Notra API on every call. OAuth connections ignore the header because each token is bound to the workspace chosen at consent.

For self-hosted HTTP deployments, OAuth validation can be configured with:

WORKOS_AUTHKIT_DOMAIN=oauth.usenotra.com
WORKOS_CLIENT_ID=client_xxx
NOTRA_MCP_RESOURCE=https://mcp.usenotra.com

The issuer is https://{WORKOS_AUTHKIT_DOMAIN} and must match the iss claim in tokens minted by AuthKit; a mismatch causes every bearer token to be rejected. Token signatures are verified against https://{WORKOS_AUTHKIT_DOMAIN}/oauth2/jwks.

When NODE_ENV=development, the default AuthKit domain is essential-berry-67-development-2.authkit.app; production defaults to oauth.usenotra.com. auth.usenotra.com is the WorkOS Authentication API domain and serves none of the OAuth endpoints, so it does not work here.

Hosted usage statistics

The HTTP server reports MCP usage to Notra's MCP server analytics through @usenotra/geo/mcp. Every tools/list and tools/call request is recorded with its method, tool name, status (ok, tool_error or rpc_error), latency, response size, and the server name and version. tools/list answers also record the advertised tools. Local stdio servers do not emit usage events.

Set the Notra GEO token on the hosted deployment to enable tracking:

NOTRA_GEO_TOKEN=your-geo-token

Without a token, tracking is disabled. OAuth calls are attributed to the WorkOS user_id; API-key calls carry no user. Unknown tool names are recorded as unknown. Tool arguments and results are never sent. Delivery is batched, asynchronous and best-effort: a failed delivery logs a credential-free warning without failing the tool call.

Toolsets

All 144 tools are exposed by default, which costs roughly 23k tokens of agent context (about 12k for geo alone, 11k for content). To load only what you need, pick toolsets with NOTRA_MCP_TOOLSETS (stdio and HTTP) or the toolsets query parameter on the remote endpoint:

Toolset

Tools

content

Posts, Sites, brand identities, integrations, schedules, event triggers, webhooks, skills, feedback inbox

geo

Projects and every GEO tool

Workspace tools and submit_feedback are always available.

NOTRA_MCP_TOOLSETS=content npx -y @usenotra/mcp
https://mcp.usenotra.com/mcp?toolsets=geo

Tools

Workspace

Tool

Description

whoami

Show the current workspace and authenticated account information

list_workspaces

List accepted and pending workspaces available to the authenticated account

Each MCP connection operates in the workspace bound to its bearer token, or for account API keys the workspace selected with NOTRA_ORGANIZATION_ID or the X-Notra-Organization-Id header. To act in another workspace, authorize or configure a separate connection for that workspace; list_workspaces discovers access but does not switch workspaces.

Posts

Tool

Description

list_posts

List post summaries with optional filters for sorting, pagination, status, content type, and brand identity

get_post

Get a single post by ID

get_post_agent_reach

AI crawler, citation and referral visits to a post's live page on its Notra Site

create_post

Create a post from your own title and markdown

update_post

Update a post's title, markdown, status, or credited authors

delete_post

Delete a post

generate_post

Queue async post generation from GitHub activity, one pull request, or your own brief

get_post_generation_status

Check the status of a post generation job

create_post_pull_request

Open a draft GitHub pull request for a saved blog post or changelog

get_post_schedule

Get a post's publishing schedule and per-destination status

schedule_post

Schedule an existing post for publishing in Notra and optionally GitHub, X, or LinkedIn

cancel_post_schedule

Cancel pending publishing destinations; already-publishing destinations finish on their own

To turn a pull request into a post, call generate_post with pullRequest (owner, repo, number) and optionally a brief, poll get_post_generation_status for the postId, then call create_post_pull_request to open a draft pull request with the post. Calling it again updates that pull request. A brief also works on its own to say what a post from recent activity should cover.

Post publishing schedules are separate from the content-generation schedules below. schedule_post requires an ISO 8601 scheduledAt timestamp, accepts an optional IANA timeZone (default UTC), and supports at most two external destinations. GitHub destinations use repositoryId from list_integrations and an optional merge flag (default true); social destinations use a connected X or LinkedIn accountId. Omitting destinations schedules publishing in Notra only.

Sites

Notra Sites are hosted blogs and changelogs built from a GitHub repository. Settings, domains, rollbacks and deletion stay in the dashboard. These tools need the sites.read and sites.write scopes.

Tool

Description

list_sites

List Notra Sites with their URL, live state and blog mount

get_site

Get a Site's settings, live deployment, custom domains and open previews

list_site_deployments

List production and preview builds with status, commit and compiler diagnostics

get_site_deployment

Get one deployment with its diagnostics and build log

deploy_site

Build and publish the newest commit on the production branch

redeploy_site_deployment

Rebuild the same commit, for example to retry a failed build

preview_post_on_site

Build a private preview of a Site with a saved post added, without touching the repository

get_site_post_preview

Get the status and URL of a post's preview

publish_post_to_site

Open or update a pull request that adds a post to the Site's repository; it goes live once merged

list_site_authors

List a site's blog.json authors, unpublished changes included, with post usage

upsert_site_author

Create or replace a site author, or rename one with previousId

delete_site_author

Remove a site author

import_site_authors

Copy Notra authors into a site's blog.json

set_site_author_page

Set the author page layout (inline or stacked)

update_site_sections

Choose which of the blog and changelog the Site serves, and their paths

publish_site_design

Publish the site's unpublished blog.json changes and deploy it

publish_post_to_site always opens or updates a pull request, even when the repository publishes directly from the dashboard.

Author changes are saved to the site's blog.json as unpublished Design changes, the same draft the dashboard's Design tab shows, and go live with publish_site_design or the dashboard's Publish. Author ids are 1 to 40 lowercase letters, digits and dashes, and links must be https:// URLs. Renaming or deleting an author that is live or credited on posts needs force. publish_site_design refuses while other files on the site have unpublished changes. To credit a site author on a blog post, pass its site:<id> ref in update_post's authorIds.

Brand Identities

Tool

Description

list_brand_identities

List all brand identities

get_brand_identity

Get a single brand identity by ID

update_brand_identity

Update brand identity settings

delete_brand_identity

Delete a brand identity

list_brand_colors

List a brand identity's guideline colors

create_brand_color

Add a brand color

update_brand_color

Update a brand color

delete_brand_color

Delete a brand color

generate_brand_identity

Queue async brand identity generation from a website URL

get_brand_identity_generation_status

Check the status of a brand identity generation job

Integrations

Tool

Description

list_integrations

List enabled GitHub and Linear integrations

create_github_integration

Connect a public GitHub repository

list_github_activity

List merged PRs, commits or releases of a connected repository

delete_integration

Delete a GitHub or Linear integration

Schedules

Tool

Description

list_schedules

List scheduled content generation jobs

create_schedule

Create a schedule from GitHub and/or Linear

update_schedule

Change only the fields you pass on a schedule

delete_schedule

Delete a scheduled content generation job

run_schedule

Run a schedule once now (uses AI credits)

list_schedule_runs

List a schedule's recent runs and their posts

Event Triggers

Tool

Description

list_event_triggers

List triggers that generate content from GitHub releases or pushes

get_event_trigger

Get a single event trigger by ID

create_event_trigger

Create an event trigger

update_event_trigger

Replace an event trigger's configuration

delete_event_trigger

Delete an event trigger

Webhooks

Tool

Description

list_webhook_endpoints

List HTTPS endpoints subscribed to Notra events

delete_webhook_endpoint

Remove a webhook subscription and cancel unsent deliveries

list_webhook_deliveries

List webhook deliveries, optionally filtered by status

get_webhook_delivery

Get a delivery's payload and attempt history

retry_webhook_delivery

Retry a failed webhook delivery

Skills

Tool

Description

list_skills

List reusable writing skills

get_skill

Get a single skill by name

create_skill

Create a reusable writing skill

update_skill

Update a reusable writing skill

delete_skill

Delete a reusable writing skill

Projects

GEO features are scoped to a project. Most GEO tools take a projectId; call list_projects first to find it. GEO tools require an organization-scoped API key and the GEO plan.

Tool

Description

list_projects

List the organization's GEO projects

get_project

Get a single project by ID

create_project

Create a project seeded from its brand's website

update_project

Rename a project or relink its brand identity

delete_project

Delete a project and all of its GEO data (cascading)

GEO settings

Tool

Description

get_geo_settings

Get tracked company, aliases, languages, engines and scan config

list_geo_engines

List the engine IDs a project can track

update_geo_settings

Change only the given settings and restart the scan cycle

GEO prompts and sequences

Tool

Description

list_geo_prompts

List tracked prompts (custom and auto-derived)

create_geo_prompt

Track a new prompt

update_geo_prompt

Enable or disable a tracked prompt

delete_geo_prompt

Stop tracking a prompt

import_geo_prompts

Bulk import prompts from rows or CSV

list_geo_prompt_suggestions

List prompts suggested from Search Console queries

accept_geo_prompt_suggestion

Track a suggested prompt

dismiss_geo_prompt_suggestion

Dismiss a suggested prompt

list_geo_sequences

List multi-turn prompt sequences

create_geo_sequence

Create a prompt sequence

update_geo_sequence

Update a sequence's name, steps or enabled state

delete_geo_sequence

Delete a sequence

run_geo_sequence

Run a sequence now; consumer apps queue a scan (uses AI credits)

GEO personas

Tool

Description

list_geo_personas

List buyer personas with their profile, memories and conversation prompts

update_geo_persona

Turn a persona on or off, or edit its details (clears its conversation prompts)

archive_geo_persona

Archive a persona; its past results stay readable

restore_geo_persona

Restore an archived persona, disabled

get_geo_persona_results

Get one scan's persona conversation turns per engine

get_geo_persona_activity

Get daily checks and mentions per persona

run_geo_persona

Play a persona's conversation now; consumer apps queue a scan (uses AI credits at 2x)

generate_geo_personas

Generate a full set, add one from a brief, or regenerate one (uses AI credits)

get_geo_persona_generation_status

Check the latest persona generation job

GEO competitors

Tool

Description

list_geo_competitors

List tracked competitors

upsert_geo_competitor

Create, update or rename a competitor

suggest_geo_competitors

AI-discover likely competitors for a domain

delete_geo_competitor

Stop tracking a competitor

import_geo_competitors

Bulk import competitors from rows or CSV

GEO scans and visibility

Tool

Description

create_geo_scan

Trigger an async visibility scan (uses AI credits)

rescan_geo_prompt

Scan a single prompt again (uses AI credits)

list_geo_scans

List scans with pagination

get_geo_scan

Get a scan and its status

get_geo_snapshot

Compact cross-signal diagnosis and recommended next actions

get_geo_changes

Changes between the two latest scans

get_geo_visibility_overview

Mention rates per answer engine

get_geo_visibility_timeseries

Daily mention counts per engine

list_geo_prompt_result_summaries

Filtered, paginated results without full answers or URLs

get_geo_prompt_result_detail

Full answer and sources for one check

get_geo_prompt_history

Compact historical checks for one prompt

get_geo_sentiment

Sentiment metrics and previous-period comparison

get_geo_sentiment_analysis

Stored thematic sentiment analysis

list_geo_sentiment_evidence

Paginated answers behind sentiment metrics

list_geo_shelf_sources

Paginated citation shelf and opportunity state

get_geo_competitor_share

Top brands by share of voice, with brand filter and limit

get_geo_language_share

Mention rates per tracked language

get_geo_competitor_detail

One competitor's mention history and the prompts driving it

GEO content briefs

Tool

Description

list_geo_content_gaps

Prompts where competitors are mentioned and this brand is not

update_geo_content_gap

Ignore a prompt gap or restore it

list_geo_content_briefs

List content briefs and their statuses

plan_geo_content_brief

Research a topic and plan a brief (billed, can take minutes)

get_geo_content_brief

Get a brief with the full document and writer status

update_geo_content_brief

Edit a draft brief's outline and planning fields

approve_geo_content_brief

Approve a brief and start the article writer

Agent readiness

Tool

Description

get_geo_agent_readiness

Latest readiness report, score history and any scan in flight

start_geo_agent_readiness_scan

Queue a readiness scan of the project's website

AI traffic

Tool

Description

get_geo_traffic_overview

Crawler and AI-referral totals, sources and daily timeseries

get_geo_traffic_log

Most recent individual AI crawler/referral requests

list_geo_traffic_journeys

Sessions grouped by journey

get_geo_traffic_journey

Every event in one journey

list_geo_traffic_pages

Most visited pages by AI traffic

get_geo_traffic_journey_stats

Journey counts per AI source and per page

get_geo_ingest_setup

Install snippets, log drain URLs and the notra.js web key

Website analytics

Page views and outbound link clicks from the notra.js script, plus history imports. Rotate the web key and start imports in the dashboard.

Tool

Description

get_geo_web_analytics

Views, visitors, sessions and AI visitors against the previous window, daily trend and hosts

get_geo_web_analytics_breakdowns

Pages, sources, countries, devices, languages, outbound links, vitals and errors

get_geo_web_analytics_utm

Sessions per UTM source, medium, campaign, term or content

list_geo_analytics_imports

History imports and their progress

MCP server analytics

Usage of your own MCP server, reported by the @usenotra/geo SDK. Captured arguments, responses and end-user IDs stay in the dashboard.

Tool

Description

get_geo_mcp_analytics

Calls, errors, latency, clients, models, intents, recent failures and unused tools

get_geo_mcp_tool_analytics

One tool's failures and the tools agents call right before and after it

Feedback

Tool

Description

submit_feedback

Send a bug report, feature request, question or praise to the Notra inbox (no auth)

list_feedback

List feedback the organization received, by status, kind or project

get_feedback

Get one feedback entry with agent metadata

update_feedback

Set a feedback entry's triage status

Review and data boundaries

All supported operations are listed upfront by tools/list. General-purpose agent execution and approval tools are not exposed because they can run dynamically discovered third-party operations. Chat history and agent sessions are available through the dashboard and API. Use the Notra dashboard for agent conversations, private-repository authentication, webhook signing secrets, and traffic tracking credentials.

Tool inputs are for task-specific business content. Do not send health records, biometric data, government identifiers, payment card information, credentials, or unrelated conversation history. Authenticate through OAuth or local configuration, never through tool arguments. Feedback accepts only the user-approved message, optional title, and feedback kind.

Development

Use Node 24 and the pnpm version pinned in package.json:

corepack enable
pnpm install --frozen-lockfile
pnpm run typecheck
pnpm run format:check

Tool output schemas in src/schemas/api-responses.ts are generated from the Notra OpenAPI spec. Run pnpm run generate:output-schemas after the API changes; CI fails when the file is stale.

CI runs typechecking, formatting checks, and the build on pull requests and pushes to main.

Available Tools

30 tools
create_chatAInspect

Start a new chat and return the assistant's reply text with the chat ID when available

Inputs: message (required), model, context, timezone, +3 more.

create_github_integrationCInspect

Connect a GitHub repository as an integration for content generation

Inputs: repo (required), owner (required), token, branch.

create_scheduleBInspect

Create a content generation schedule using a cron-style daily, weekly, or monthly trigger

Inputs: name (required), enabled (required), targets (required), outputType (required), +5 more.

create_skillBInspect

Create a reusable writing skill

Inputs: name (required), content (required), description (required).

delete_brand_identityB
DestructiveIdempotent
Inspect

Delete a brand identity. Returns any schedules or events that were disabled as a result.

Inputs: brandIdentityId (required).

delete_integrationA
DestructiveIdempotent
Inspect

Delete a GitHub or Linear integration. Returns any schedules or events that were disabled as a result.

Inputs: integrationId (required).

delete_postB
DestructiveIdempotent
Inspect

Delete a post by its ID

Inputs: postId (required).

delete_scheduleA
DestructiveIdempotent
Inspect

Delete a content generation schedule by its ID

Inputs: scheduleId (required).

delete_skillA
DestructiveIdempotent
Inspect

Delete a reusable writing skill by name

Inputs: name (required).

generate_brand_identityAInspect

Queue async brand identity generation from a website URL. Notra will scrape the site and extract brand info. Use get_brand_identity_generation_status to poll for completion.

Inputs: websiteUrl (required), name.

generate_postAInspect

Queue an async post generation job. Notra will analyze your GitHub activity and generate content. Use get_post_generation_status to poll for completion.

Inputs: contentType (required), github, dataPoints, brandVoiceId, +6 more.

get_brand_identityA
Read-only
Inspect

Get a single brand identity by its ID, including tone, audience, and language settings

Inputs: brandIdentityId (required).

get_brand_identity_generation_statusA
Read-only
Inspect

Check the status of an async brand identity generation job

Inputs: jobId (required).

get_chatA
Read-only
Inspect

Get a single chat session with its messages

Inputs: chatId (required).

get_chat_by_external_channelA
Read-only
Inspect

Get a chat session by Discord or Slack external channel ID

Inputs: id (required), source (required).

get_postA
Read-only
Inspect

Get a single post by its ID, including full content in HTML and markdown

Inputs: postId (required).

get_post_generation_statusA
Read-only
Inspect

Check the status of an async post generation job. Returns job status and event log.

Inputs: jobId (required).

get_skillA
Read-only
Inspect

Get a single reusable writing skill by name

Inputs: name (required).

list_brand_identitiesA
Read-only
Inspect

List all brand identities configured for your organization

Inputs: no named parameters.

list_chatsA
Read-only
Inspect

List chat sessions for your organization

Inputs: no named parameters.

list_integrationsA
Read-only
Inspect

List all connected integrations (GitHub, Slack, Linear) for your organization

Inputs: no named parameters.

list_postsA
Read-only
Inspect

List posts from Notra with optional filters for sorting, pagination, status, content type, and brand identity

Inputs: page, sort, limit, status, +2 more.

list_schedulesA
Read-only
Inspect

List scheduled content generation jobs, optionally filtered by repository IDs

Inputs: repositoryIds.

list_skillsA
Read-only
Inspect

List reusable writing skills for your organization

Inputs: no named parameters.

post_chat_messageBInspect

Post a message to an existing chat and return the assistant's reply text

Inputs: chatId (required), message (required), model, context, +4 more.

submit_feedbackAInspect

Send product feedback, a bug report, or a feature request to the Notra team

Inputs: message (required), sentiment.

update_brand_identityA
DestructiveIdempotent
Inspect

Update a brand identity's settings including name, tone, audience, language, and more

Inputs: brandIdentityId (required), name, audience, language, +7 more.

update_postA
DestructiveIdempotent
Inspect

Update a post's title, markdown content, or publication status

Inputs: postId (required), slug, title, status, +1 more.

update_scheduleB
DestructiveIdempotent
Inspect

Update an existing content generation schedule

Inputs: name (required), enabled (required), targets (required), outputType (required), +6 more.

update_skillC
DestructiveIdempotent
Inspect

Update a reusable writing skill by name

Inputs: currentName (required), name, content, description.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 30 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action. Post, brand identity, integration, schedule, chat, skill, and feedback tools are clearly separated. Async generation and status polling are paired cleanly, avoiding ambiguity.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (e.g., delete_post, create_skill). Minor inconsistencies: 'create_github_integration' is more specific than 'delete_integration', and 'submit_feedback' deviates from the create/update/delete pattern.

    Tool Count4/5

    30 tools cover multiple subdomains (posts, brand, integrations, schedules, chats, skills, feedback). While slightly high, each tool serves a clear purpose and most CRUD operations are present, making the count reasonable.

    Completeness4/5

    Core CRUD operations are present for posts, brand identities, skills, schedules, and chats. Async generation with polling is implemented. Missing update/delete for integrations and feedback lifecycle (no list/update/delete for feedback) are minor gaps.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers