Koskamo

Invitt MCP

An MCP server that enables AI assistants to plan events, suggest venues, manage guest lists, send invitations and reminders, and track RSVPs via OAuth authentication.

Visit Invitt

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

Invitt MCP logo, by InvittVendor evidenceStreamable HTTPOAuth sign-inEndpoint checked 2026-11-01Operated by Invitt
You need:Add the endpoint below as a custom connector in your assistant and sign in when it asksInvitt uses OAuth, so your assistant never sees a password and there's no client secret to manageNew accounts start with lower limits, which go up once the account is established
MCP endpoint (Streamable HTTP)
https://agent.invitt.net/mcp
Vendor documentation

What you can do with it

  • Plan a team offsite or client dinner
  • Send invitations and reminders to guests
  • Track RSVP status and manage guest lists
  • Recommend locations for events

Source and maintenance

Vendor evidenceRegistry 1.0.0
mcp-registry: net.invitt/invitt@1.0.0Source repositoryProject website
Maintenance checked

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
250 ms
95th percentile latency
250 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 250 ms · metadata changed · refuses unauthenticated initialize (HTTP 401)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http invitt-mcp https://agent.invitt.net/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add invitt-mcp --url https://agent.invitt.net/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable invitt-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "invitt-mcp": {
      "url": "https://agent.invitt.net/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "invitt-mcp": {
      "type": "streamableHttp",
      "url": "https://agent.invitt.net/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start invitt-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "invitt-mcp": {
      "type": "http",
      "url": "https://agent.invitt.net/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http invitt-mcp https://agent.invitt.net/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "invitt-mcp": {
      "url": "https://agent.invitt.net/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "invitt-mcp": {
      "serverUrl": "https://agent.invitt.net/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Invitt MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 4,441

Do you run Invitt MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing