Entry

fyi.entry由 entry.fyi 發布官方發布者v1.0.0更新於 Oct 29, 2026

Read your Entry profile and drafts, write drafts and request publication. You approve changes.

已驗證Streamable HTTP可網頁執行效率與工作流知識與記憶

服務詳細資訊

識別碼: fyi.entry/entry
傳輸: Streamable HTTP
執行環境: Web executable
信任: Verified
發布於: Oct 29, 2026

安全提示

MCP 服務會接收對話中的工具呼叫請求，並可能執行外部操作。啟用前請先了解該服務能做什麼，並只授予它所需的權限。

註冊中心已驗證此服務的命名空間屬於 entry.fyi，且該網域同時執行其端點。這可以確認發布者，但並不代表該服務的工具是安全的。

SourceWeft 的檢查只涵蓋條目是否完整、端點是否回應；不審查伺服器的程式碼，也不審查其工具的行為。

在 README 中新增徽章

向讀者展示該 MCP 服務已收錄於 SourceWeft，徽章連結到本頁。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/fyi.entry%2Fentry.svg)](https://sourceweft.com/mcp/fyi.entry%2Fentry?utm_source=readme&utm_medium=badge)

概覽

AI 產生的概覽

Entry 遠端伺服器，讓助理讀取你的 Entry 個人頁面與草稿、撰寫草稿，並提出個人頁面變更或發布請求供你核准。

可以做什麼: 列出並讀取可觸及的 Entry、個人頁面（含未發布欄位）與草稿，每次 20 筆
建立與更新私人草稿，依上次讀取的版本儲存變更
提出個人頁面變更，例如名稱、標題、簡介、地點、連結與可合作狀態
請求發布草稿，並查詢請求狀態：待處理、已發布、遭拒、已過期或已撤回
適用情境: 適合擁有 Entry 個人頁面、希望助理協助草擬文章、修改既有草稿或準備個人頁面調整，同時由自己保留最後決定權的人。它無法直接發布或更動線上頁面，因此不適合需要助理直接上線內容的情境。
執行需求: 遠端 Streamable HTTP 端點，以 OAuth 登入；無需安裝，也沒有 API 金鑰。登入時需選擇要分享哪些 Entry，以及授予五項權限中的哪些。測試時可使用個人存取權杖。

安裝前請注意

助理可讀取未發布的個人頁面欄位與草稿，請只授權必要的 Entry 與權限範圍。它能建立與覆寫草稿內容，並提出個人頁面變更與發布請求；這些都會出現在 Entry 中由你核准或拒絕，未經核准不會上線。可於設定 → 整合中斷連線以撤銷存取。

安裝

在 SourceWeft 中

開啟儀表板中的 Entry，將其新增到工作區。
連接所需的憑證。它們會被私密儲存，絕不會在公開頁面上展示。
為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/fyi.entry%2Fentry/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。客戶端會在首次連接時完成 OAuth 登入。

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

README

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.

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 Code

Then, inside Claude Code, run /mcp and sign in to Entry in your browser. Add --scope user to use it in every project.

Or install the plugin, which adds the server and the Entry skills:

Claude (claude.ai and desktop)

Open Customize → Connectors and choose Add custom connector. On Team and Enterprise plans an Owner adds it under Organization settings → Connectors → Add → Custom, and members then press Connect.
Name it Entry and paste https://entry.fyi/mcp.
Choose Add. Claude sends you to Entry: sign in, tick the Entries to share and choose Allow.
In a new chat press +, then Connectors, and turn Entry on.

ChatGPT

Open ChatGPT Plugins. If your plan needs developer mode, turn it on first under Settings → Apps → Advanced.
Select +, then Add custom MCP server. Name it Entry.
Under Connection, paste https://entry.fyi/mcp. For authentication choose OAuth and leave any client ID and secret empty.
Read the risk warning, confirm, and create it.
ChatGPT sends you to Entry. Sign in, tick the Entries to share and choose Allow. Start a new chat and turn Entry on for it.

Cursor

Add to Cursor

Or add it to ~/.cursor/mcp.json:

VS Code

Add to VS Code · Add to VS Code Insiders

Or add it to .vscode/mcp.json:

Codex CLI

Or add it to ~/.codex/config.toml:

Gemini CLI

That adds the server and the Entry skills. Or add just the server:

Then, inside the Gemini CLI, run /mcp auth entry and sign in in your browser.

Antigravity CLI

Add it to ~/.gemini/config/mcp_config.json:

Zed

Add it to your settings.json:

Grok

Open Grok connectors. On Grok Business and Enterprise a team admin adds Entry first, in the xAI console under Grok Business → Connectors → Add Connector → Other.
Choose New Connector, then Custom. Name it Entry and paste https://entry.fyi/mcp as the Server URL.
Choose Add Connector. Grok sends you to Entry: sign in, tick the Entries to share and choose Allow.

Any other MCP client

Entry is a standard remote server, so any client that supports remote servers with OAuth works. A typical configuration:

Where your client wants a key other than url, the URL goes in the same place.

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

Tool	What it does	Writes?
`list_entries`	Lists the Entries this connection can reach	no
`get_entry_profile`	Reads a profile as the owner sees it, including unpublished fields	no
`list_drafts`	Lists working or published drafts, 20 at a time	no
`get_draft`	Reads one draft in full, with its revision	no
`create_draft`	Creates a private draft	adds a draft
`update_draft`	Saves changes to a draft against the revision last read	overwrites the fields sent
`propose_profile_update`	Proposes profile changes for the owner to approve	adds a proposal
`request_publication`	Asks the owner to publish a draft	adds a request
`get_publication_status`	Checks a publication request: pending, published, rejected, stale or withdrawn	no

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:

Scope	Lets the assistant
`profile:read`	Read your profile
`drafts:read`	Read your drafts and posts
`drafts:write`	Create and edit drafts
`profile:propose`	Propose profile changes
`publish:request`	Ask you to publish a draft

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


Endpoint	`POST https://entry.fyi/mcp`
Transport	Streamable HTTP, stateless, JSON responses (no sessions, no SSE). `GET` and `DELETE` are `405`
Auth	OAuth 2.1: authorization code with PKCE S256, dynamic client registration or a Client ID Metadata Document, `resource=https://entry.fyi/mcp` (RFC 8707)
Discovery	`401` with `WWW-Authenticate: Bearer resource_metadata="https://entry.fyi/.well-known/oauth-protected-resource/mcp"`
Authorization server	`https://entry.fyi/.well-known/oauth-authorization-server`
Personal access tokens	`Authorization: Bearer entry_pat_…`, made in Settings → Integrations, for testing with MCP Inspector
Limits	120 reads and 30 writes a minute per connection; refusals carry `Retry-After` or `details.retryAfter`
MCP Apps	Cards for profiles, drafts and publication requests (`ui://entry/*`) in hosts that support them

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):

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).