Skip to main content

How do I approve the LaunchNotes MCP connector for my organization?

For workspace owners and IT/security admins: what the LaunchNotes MCP connector can access, how LaunchNotes roles scope it, and how to approve it for Claude Team or Enterprise.

What is LaunchNotes?

LaunchNotes is a product communication platform — one place to publish product announcements, maintain a public or private roadmap, and collect customer feedback. Product and marketing teams use it to keep customers and internal teams current on what's shipping.

This guide is for workspace owners and IT/security admins evaluating or approving the LaunchNotes connector for Claude (Team or Enterprise). For the step-by-step instructions each team member follows, see How do I connect AI assistants to my LaunchNotes workspace?

What the connector is

A LaunchNotes-hosted MCP server at https://mcp.launchnotes.com/mcp. Once connected, a team member's AI assistant can work in LaunchNotes on their behalf — drafting and publishing announcements, managing roadmap items, assigning categories, searching, reading feedback, and pulling analytics — instead of clicking through the app.

All traffic is over HTTPS. The server is stateless: it holds no session data between requests.

How sign-in works

  • Each person connects with their own LaunchNotes account through a standard OAuth browser login. There are no API keys or shared credentials to create, distribute, rotate, or store.

  • That means each user needs their own LaunchNotes account with access to the relevant project(s). See How do I add team members and manage roles in LaunchNotes?

  • Every request carries a signed token that the MCP server verifies before it reaches any tool — including the initial handshake and the request that lists available tools.

  • The assistant acts as that user, with exactly their permissions. Nothing is elevated.

Access is scoped to the user's LaunchNotes role

This is the main control you have. The connector checks the signed-in user's role on every request and only offers the tools that role permits. A user without publishing rights isn't given a publish tool at all — the assistant can't see it, let alone call it.

Because the check runs per request, role changes take effect immediately — no reconnect required.

LaunchNotes role

Read announcements, roadmap, feedback, analytics

Create & edit drafts and roadmap items

Publish, schedule, or archive announcements

Move roadmap items between stages

Change project settings (colors, content, features, custom code)

Admin

✅

✅

✅

✅

✅

Publisher

✅

✅

✅

✅

—

Publisher – Announcements

✅

✅

✅

—

—

Publisher – Roadmap

✅

✅

—

✅

—

Contributor

✅

✅

—

—

—

Project Feedback Agent

✅

File feedback only

—

—

—

Project Viewer

✅

—

—

—

—

A user with no role on any project gets a single tool — the one that lists the projects they can see — and nothing else.

What can notify your customers

Two connector actions can send email to people outside your company. Both are gated by role, and both are designed to require your team member's explicit go-ahead:

  • Publishing or scheduling an announcement (requires publish rights) fires whatever notifications are already configured on that announcement — often nothing, since drafts default to public-page only. The assistant can check the notification posture beforehand and is instructed to confirm with the user before publishing anything that will email or Slack subscribers.

  • Posting a roadmap update (requires roadmap create/edit rights, so Contributors can do this) can email the people following that item. The tool requires the assistant to look up and state the exact audience — for example, "this will email 25 subscribers and 1 team member" — and get confirmation before posting. It also supports an internal-only mode that notifies no one.

LaunchNotes' bundled skills are written draft-first for the same reason: they prepare the work and leave anything customer-facing for a human to approve.

One caveat worth stating plainly: these confirmation steps are instructions the assistant follows, not server-side blocks. If you want a strict guarantee that a given person can never trigger a customer email, control it with their role, not with the connector.

What the connector can't do

  • No deletes. The LaunchNotes API has no delete operation for this surface — announcements can only be archived.

  • Analytics are aggregate only — engagement counts, subscriber totals, feedback sentiment. There is no tool that exports subscriber lists or personal data.

  • Rate limited to 300 operations per 5 minutes; requests beyond that return an error.

  • No cross-tenant access. The connector can only reach projects the signed-in user already has access to.

Approving it for your organization (Claude Team / Enterprise)

In managed Claude workspaces, connectors are enabled at the organization level by an Owner or Primary Owner — members who try to add one themselves are prompted to contact an organization owner instead.

An owner can:

  1. Add the connector in the Claude organization's connector settings, using the remote MCP URL https://mcp.launchnotes.com/mcp — or install the LaunchNotes plugin, which bundles the connector along with LaunchNotes' skills.

  2. Members then connect individually and sign in with their own LaunchNotes account.

For the exact Claude admin screens, see Anthropic's connector documentation.

Claude Code installs per user, so people using the CLI can connect without organization-level approval. Their access is still bounded by their LaunchNotes role.

Removing access

  • Offboarding one person: remove or downgrade their LaunchNotes role. It applies on their next request — you don't need to touch anything in Claude.

  • Turning it off org-wide: remove the connector (or plugin) in your Claude organization settings.

  • Individually: a user can disconnect LaunchNotes from their own Claude connector settings at any time.

Security and compliance questions

For our certifications, subprocessors, data handling, and infrastructure details, see the LaunchNotes security posture. If your review needs something that isn't covered there, reach out and we'll get you an answer.

Notes & important info

  • The MCP connector is currently in beta. Features and functionality may evolve.

  • The legacy setup — a LaunchNotes API token run locally via npx — is frozen as of August 2026. If your team is still using it, the end-user guide covers migrating off it and revoking the old token.

Related Articles
Did this answer your question?