Entry

Entry MCP Server

Connect your AI assistant to Entry, your personal page and your writing. The assistant can read your profile and drafts, write and edit drafts, propose profile changes and ask you to publish. You approve every public change in Entry.

https://entry.fyi/mcp

A remote MCP server: Streamable HTTP, signed in with OAuth. There's nothing to install or run, and no API key. When your client connects, Entry asks you to sign in and choose which of your Entries to share and what the assistant may do.

Quick Start

Cursor

Add to Cursor

Click the link above to add Entry to Cursor. When Cursor asks, sign in to Entry and choose which Entries to share. The Entry MCP tools will appear in your agent chat.

What you can do:

• "Show my Entry profile and drafts"
• "Create a draft post about my recent project"
• "Update my headline to reflect my new role"
• "Send this draft for publication"

How it works:

Entry is draft-and-approve. Your Cursor agent can read and propose changes, but nothing goes live until you approve it in Entry. Profile changes and publication requests appear under Settings → Integrations in Entry.

Grok Bot

Ask your Grok Bot agent to connect to Entry:

"Add Entry as an MCP server. The URL is https://entry.fyi/mcp"

When the OAuth card appears, sign in and choose your Entries. Then ask Grok Bot to help with your profile or writing.

Example prompts:

• "Read my Entry profile"

• "Draft a post about the feature we just shipped"

• "Propose updating my bio"

• "Check the status of my publication request"

• Connect your assistant

• What the assistant can do

• Tools

• Permissions

• For client developers

• Agent Skills

Connect your assistant

claude mcp add --transport http entry https://entry.fyi/mcp

/plugin marketplace add entry-fyi/skills/plugin install entry@entry

{  "mcpServers": {    "entry": { "url": "https://entry.fyi/mcp" }  }}

{  "servers": {    "entry": { "type": "http", "url": "https://entry.fyi/mcp" }  }}

codex mcp add entry --url https://entry.fyi/mcp

codex mcp login entry

[mcp_servers.entry]url = "https://entry.fyi/mcp"

gemini extensions install https://github.com/entry-fyi/skills

gemini mcp add --transport http entry https://entry.fyi/mcp

{  "mcpServers": {    "entry": { "serverUrl": "https://entry.fyi/mcp" }  }}

{  "context_servers": {    "entry": { "url": "https://entry.fyi/mcp" }  }}

{  "mcpServers": {    "entry": { "type": "http", "url": "https://entry.fyi/mcp" }  }}

The same steps, kept current, are at entry.fyi/developers#connect.

What the assistant can do

Try asking:

• "Show my unfinished Entry drafts."
• "Create an article about my recent work."
• "Update the introduction of this draft."
• "Prepare this article for publication."
• "Change my headline to …"

It can:

• Read your Entry as you see it, including fields you haven't published, and your drafts and posts.
• Start a draft from your idea and edit it with you. Drafts are private until you publish them.
• Propose changes to your profile: name, headline, bio, location, links, availability.
• Ask you to publish a draft when it's ready.

It can't publish, unpublish or change your live page. A profile proposal or a publication request appears in Entry, where you see exactly what would change and approve or reject it. In ChatGPT and Claude, profiles, drafts and publication requests show as cards in the chat.

Tools

Every tool has an input and output schema with Entry's field limits (maxLength, maxItems) and explicit annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint). Full schemas: entry.fyi/developers#mcp-tools.

Permissions

When you connect, you choose which Entries the assistant may reach and which of five permissions it gets:

Disconnect any time from Settings → Integrations → Connected apps in Entry; access stops on the next request. Entry shares your content with an assistant only when you ask it to use Entry, and doesn't use it to train AI models. See the privacy policy.

For client developers

Check the server answers (without a token it must be 401 with a WWW-Authenticate header, which is how a client finds Entry's sign-in):

curl -i -X POST https://entry.fyi/mcp

Tool errors are tool results with isError: true and { code, message, details }: forbidden, not_found, conflict, validation_failed, limit_reached, rate_limited, bad_request.

Entry also has a public, read-only API for published profiles (no auth) and an authenticated REST API for the same operations as this server: entry.fyi/developers, OpenAPI.

Agent Skills

entry-fyi/skills has Agent Skills that teach an agent to use Entry well: entry (this server, the right tool for each request, revisions and the approval boundary) and entry-public-profiles (looking people and companies up through the public API).

npx skills add entry-fyi/skills

Support

• Help for owners: entry.fyi/developers/support
• Bugs and requests: open an issue or email [email protected]
• Terms · Privacy