Log inSubmit server
Notra logo

Notra

Manage Notra posts, brand identities, integrations, and scheduled content generation through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Notra

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "notra": {
      "command": "npx",
      "args": [
        "-y",
        "@usenotra/mcp"
      ],
      "env": {
        "NOTRA_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

Notra MCP server connects AI clients to the Notra API for managing workspace content and brand settings. It supports post creation, editing, deletion, generation from GitHub activity, scheduling, and publishing destinations including GitHub, X, and LinkedIn. Additional tools cover brand identities and colors, GitHub and Linear integrations, workspace discovery, and recurring content-generation schedules. Use it when an agent needs to operate Notra content workflows through either a local stdio process or the hosted remote MCP endpoint.

Use cases

  • Create and update Markdown posts in a Notra workspace
  • Generate posts from connected GitHub activity
  • Manage brand identities and guideline colors
  • Schedule content generation and multi-destination publishing

Key features

  • Post lifecycle and publishing controls
  • Asynchronous post and brand generation
  • Brand identity and color management
  • GitHub and Linear integration management
  • Workspace-aware API access
  • Scheduled content-generation jobs

Tools80

What Notra lets your agent do. Expand a tool for its parameters.

Self-reported~1.2k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

11/11 checks healthy over the last 62d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · @usenotra/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars3Stargazers on the source repository.
npm downloads21Package downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Tools exposed80Callable tools this server registers over MCP.

How Notra works

What Notra MCP server does

Notra exposes workspace content operations from the Notra API through Model Context Protocol. Its tools cover the full lifecycle of posts: listing and retrieving content, creating posts from a title and Markdown, changing titles or status, deleting posts, and checking publishing schedules. Agents can also queue post generation based on GitHub activity and inspect the status of those asynchronous jobs.

Brand management is included alongside content operations. The server can list, inspect, update, and remove brand identities, as well as manage the guideline colors associated with each identity. Integration tools expose enabled GitHub and Linear connections, allow a public GitHub repository to be connected, and retrieve merged pull requests, commits, or releases from a connected repository.

Scheduled workflows are handled separately from individual post publishing. Agents can list, create, update, and delete scheduled content-generation jobs. Publishing tools can schedule an existing post in Notra and optionally send it to GitHub, X, or LinkedIn, retrieve per-destination status, or cancel destinations that have not started publishing.

How it works

The package runs as a local MCP process over stdio when launched with npx -y @usenotra/mcp. It uses a Notra API key supplied through the environment. Account-level keys can access multiple workspaces; set NOTRA_ORGANIZATION_ID when a particular workspace must be selected. The list_workspaces tool can show available workspace IDs before choosing one.

Notra also provides a hosted streamable HTTP endpoint at https://mcp.usenotra.com/mcp. Remote clients can authenticate with OAuth, or use a static Notra API key as a bearer token. A workspace-scoped URL, such as /mcp/acme, pins the connection to one workspace and is useful for clients that cannot send custom headers.

Some operations are asynchronous. Post generation and brand identity generation return jobs that can be checked with their corresponding status tools rather than completing in the initial request.

Setup and configuration

Node.js 20 or newer is required for the local package. Create an API key from the Notra workspace dashboard under Developer > API Keys, then configure the MCP client to run the package with NOTRA_API_KEY in its environment. Claude Desktop, Claude Code, Codex, Cursor, OpenCode, and Amp setup examples are supported by the project’s configuration guidance.

For hosted deployments using OAuth, self-hosted HTTP validation can be configured with WorkOS AuthKit settings including WORKOS_AUTHKIT_DOMAIN, WORKOS_CLIENT_ID, and NOTRA_MCP_RESOURCE. These settings apply to OAuth validation rather than ordinary local stdio use.

Tools and capabilities

  • Identify the authenticated account and active workspace.
  • List, create, edit, delete, generate, schedule, and publish posts.
  • Inspect post-generation jobs and destination-specific publishing status.
  • Manage brand identities and their guideline colors.
  • Connect public GitHub repositories and inspect repository activity.
  • List and remove GitHub or Linear integrations.
  • Create and maintain scheduled content-generation jobs.

Limitations and notes

The local server requires a Notra API key and Node.js 20 or newer. Account API keys need a workspace selection when the account belongs to multiple workspaces; organization keys already target their workspace. A scoped remote URL cannot switch workspaces, and its OAuth authorization must match the workspace in the URL.

Cancelling a post schedule only affects destinations that are still pending. Destinations already publishing finish independently. Legacy remote MCP sessions expire after 30 minutes of inactivity, while session limits can also reject new hosted sessions when the server-wide limit is reached.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Notra

Notra is an MCP server that connects AI clients to the Notra API for workspace content operations. Its main tools create, read, update, delete, generate, and schedule posts; manage brand identities and colors; inspect integrations; and create or maintain scheduled content-generation jobs.

Install it by configuring your MCP client to run `npx -y @usenotra/mcp` with `NOTRA_API_KEY` set in the environment. Node.js 20 or newer is required, and the API key can be created in the Notra workspace dashboard under Developer > API Keys.

Yes, Notra works with Cursor through either the local stdio package or the hosted streamable HTTP endpoint. For a remote connection, add the Notra MCP URL to Cursor’s MCP configuration; a workspace-scoped URL can pin the connection to a specific workspace.

Set `NOTRA_ORGANIZATION_ID` to the desired workspace ID or slug when using an account API key. You can first call `list_workspaces` to see accepted and pending workspaces. Organization API keys already target their workspace and ignore this variable.

Yes, the `schedule_post` tool can schedule an existing post in Notra and optionally include GitHub, X, or LinkedIn as publishing destinations. `get_post_schedule` reports per-destination status, while `cancel_post_schedule` cancels destinations that have not begun publishing.

Related MCP servers

All in Social Media All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewNotra AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/notra?style=directory)](https://allmcps.com/mcp/notra)
HTML Embed
<a href="https://allmcps.com/mcp/notra"><img src="https://allmcps.com/api/badge/notra?style=directory" alt="Notra on AllMCPs" /></a>