Context7
Up-to-date docs for AI agents
作者提供的说明(英文原文)
Edworking tasks, Docs, workspace search, conversations and files with scoped OAuth access.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://mcp.edworking.com/mcp在终端中运行这条命令
claude mcp add --transport http edworking https://mcp.edworking.com/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"edworking": {
"url": "https://mcp.edworking.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"edworking": {
"type": "http",
"url": "https://mcp.edworking.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://mcp.edworking.com/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 Edworking 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
在 214 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(0.3.0)于前天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Context7, Codebase Memory, Exa
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
The official, open-source Edworking MCP server. Connect your assistant to projects, tasks, Docs, conversations and files your account can access.
Hosted endpoint: https://mcp.edworking.com/mcp
Public identity: Edworking MCP. The Railway infrastructure retains the codename Bellsprout. Use the custom domain above for all new connections. Connections created against the earlier Railway URL must reconnect because their OAuth resource audience has changed.
Release: 0.3.0 adds a Figma plugin transport, design-aware task and Doc creation, and two frame-link tools (24 tools total). Deploy the matching scoped API backend before the MCP server. Docs require new docs:read / docs:write token permissions and OAuth consent. Existing grants are not expanded automatically.
Distribution: npm, the hosted server and Official MCP Registry are at 0.3.0. OpenAI version 0.3.0 was submitted on 5 November 2026 and is In review, not yet published. The metadata upload had no findings and its authenticated scan discovers all 24 tools. See the publication checklist for individual directory statuses.
Add the endpoint to an MCP client supporting Streamable HTTP and OAuth. Follow the browser authorization window, choose Continue in Edworking, and review the client, destination, workspace and permissions before approving. The fallback accepts a dedicated scoped token created in Edworking → Profile → API tokens and entered directly on the browser consent page. Never paste a token into an assistant conversation.
Connections request read permissions by default. Writes require the matching OAuth scope and upstream token permission. Reconnect with explicit scopes if your client cannot request additional permissions. Revoke the dedicated token in Edworking to disconnect every grant using it. Grants expire within 30 days or when the Edworking token expires, whichever is sooner. Access tokens last up to ten minutes and refresh tokens rotate.
codex mcp add edworking-mcp --url https://mcp.edworking.com/mcp
codex mcp login edworking-mcp
For ChatGPT testing, use Plugins → Add custom MCP server, select OAuth and enter the endpoint. Availability depends on your plan and workspace policy. A portable OpenAI plugin package is in plugin/. The 0.3.0 package declares six read and five write OAuth scopes, including Docs. The OpenAI 0.3.0 package is in review; publication awaits approval. Verify the actual consent screen and get_connection result. On 13 October, the submission portal metadata grant used five read scopes, while a separate ChatGPT demo connection received all nine scopes and successfully created a task and sent a message. Existing read-only grants remain read-only until reauthorized; a token with write permissions does not automatically upgrade an OAuth grant.
Other clients should configure a remote HTTP server named edworking-mcp and use their built-in OAuth flow. Public clients with PKCE, dynamic registration and HTTPS Client ID Metadata Documents are supported. /mcp accepts only Edworking MCP access tokens.
Client setup instructions: Edworking MCP guide. See the competitor review and delivery roadmap for remaining capabilities and launch gates.
After Allow access or Cancel, the browser returns to your assistant automatically. If it remains on Returning to your assistant, use the return button. Each consent request can be used once and expires after ten minutes. If you see invalid_grant or an expired/used request, start a new connection from your assistant instead of reopening the old consent link. Do not refresh or resubmit the approval form.
| Tool | Scope | Purpose |
|---|---|---|
get_connection | Any connection | Connection name, permissions and expiry |
list_projects, list_project_statuses, list_project_members | projects:read | Projects, valid statuses and existing assignee IDs |
list_tasks, get_task | tasks:read | Filter tasks by project, status, assignee, priority, title and due dates; read task content |
list_figma_tasks | tasks:read | Find accessible tasks linked to a Figma file or frame |
link_figma_frame | tasks:write | Link a Figma frame to an accessible task |
search, fetch | Per-source read scope | Indexed tasks, Docs, files and project messages; typed result retrieval |
list_docs, get_doc | docs:read | Find Docs and read their Markdown content |
create_doc, update_doc, edit_doc_content | docs:write; body edits also need docs:read | Create, rename and edit Docs |
list_conversations | chats:read | Existing private conversations |
read_messages | messages:read | Accessible conversation messages |
list_files | files:read | File metadata |
create_task, update_task, edit_task_content | tasks:write; body edits also need tasks:read | Create tasks; edit name, status, priority, assignees, dates and description |
send_message | messages:write | Send the user's specified message |
create_project | projects:write | Create a project |
upload_file | files:write | Import a public HTTPS file |
Attaching files to tasks also requires files:write. Lists use cursors and at most 100 items per page; keep ordering and filters unchanged while paging. Search uses the workspace index and returns up to 20 ranked results per permitted source. It rechecks live access, deletion state and message-history limits before exposing snippets. Indexing may lag; unavailable sources are reported, and private chats and projectless items are excluded. Use filtered lists for exhaustive task discovery. File fetches return metadata, not file contents.
Read a task or Doc before editing its body. Content reads are capped at 20,000 characters and expose block handles; targeted edits reuse the collaboration service and version history. Large removals require explicit allowRemoval. A task assignee list replaces the current list: omit it to preserve, or use [] to unassign. Assignees must already belong to the project and workspace. Deletion, invitations, task moves and sharing changes are not exposed.
Writes require a UUID requestId; reuse it with unchanged arguments on retries. Completed results are encrypted and cached for 24 hours. An uncertain result is never repeated automatically: inspect Edworking before deciding what to do. This is not an upstream exactly-once transaction. Deduplication expires after 24 hours.
Use Node 24 LTS (minimum 22.19). No OpenAI API key is needed.
npm ci
cp .env.example .env
node -e "console.log(require('crypto').randomBytes(32).toString('hex'))" npm run build node --env-file=.env dist/index.js
Run npm run check for type checking, security/integration tests and build. npm run dev starts a watcher when variables are already loaded by your shell.
For local stdio, configure your client to run npx -y @edworking/mcp@0.3.0 with EDWORKING_API_TOKEN supplied securely in its process environment, or build from source and run node /absolute/path/to/edworking-mcp/dist/stdio.js. The npm package is public. Stdio uses that token directly with Edworking and has in-memory deduplication that resets on restart.
Use the included Dockerfile, attach a volume at /data, and set:
| Variable | Value |
|---|---|
NODE_ENV | production |
PORT | 3000 |
PUBLIC_BASE_URL | Stable public HTTPS origin, without /mcp |
DATABASE_PATH | /data/bellsprout.sqlite |
TOKEN_ENCRYPTION_KEY | Random 32-byte key encoded as 64 hex characters |
EDWORKING_API_URL | https://gateway.edworking.com/ |
EDWORKING_APP_URL | https://app.edworking.com |
Keep one replica, sleeping off and deployment overlap zero. /healthz checks the process and /readyz checks SQLite. Preserve the key across deployments. Optional ALLOWED_ORIGINS adds exact browser origins, OPENAI_DOMAIN_CHALLENGE serves the OpenAI verification value, and EDWORKING_CONNECT_URL enables a native Edworking connection page only after that page has shipped.
See operations, security and publication. Contributions follow CONTRIBUTING.md. Licensed under MIT.
Deploy the matching Venusaur and Charizard changes before enabling this integration, and set EDWORKING_CONNECT_URL=https://app.edworking.com/settings/integrations?connection=mcp. Native consent issues a scoped 30-day credential directly to this server using the existing ApiToken model and issuance service, with no new table, column or migration. Users manage it in Profile → API tokens, using the existing revocation and rotation operations and their step-up checks. Rotating the token invalidates the previous connection and requires reconnecting. Manual personal-token creation keeps its existing step-up checks.
The fixed Figma client goes directly to Charizard’s /connect page for sign-in, workspace selection and explicit authorization. Its existing browser/nonce-bound handoff then finishes consent and returns through /connect/result, without another MCP approval screen. General MCP clients retain their consent flow and configured integration destination. Existing connections must reconnect to grant the seven plugin scopes (projects:read, tasks:read/write, docs:read/write, files:read/write); grants are not expanded silently.
The Edworking Figma plugin, maintained in the figma/ package of Charizard, uses /plugin/start, /plugin/poll, /plugin/refresh, /plugin/revoke, and /plugin/tool. This isolated transport permits opaque plugin origins without cookies. It accepts only its fixed OAuth client and a closed subset of the same tools. PKCE binds the browser callback and polling; client credentials never enter a Figma design. General OAuth and MCP origin restrictions are unchanged.
list_figma_tasks queries accessible tasks linked to a file or frame. link_figma_frame attaches the canonical frame URL to a permitted task. The latter can retry an uncertain response because the upstream serializable transaction is idempotent; task creation retains strict uncertain-write protection. Adding the reciprocal Dev Resource is done in Figma with addDevResourceAsync, without Figma REST OAuth.
Plugin-only helpers read account/workspace context, task lists and document folders, append native Figma blocks through the existing collaborative content service, and upload bounded attachment bytes through the existing File storage path. They are excluded from public MCP discovery; its catalog remains 24 tools. /plugin accepts up to 12 MB of JSON for an 8 MiB file; the public MCP request limit remains 256 KB. All calls retain upstream identity, workspace and permission checks. Task creation accepts optional Markdown content, priority, assignees, start date and list; document creation accepts an existing authorized folder. Legacy task description input remains supported but cannot be combined with content.
The landing page includes a Figma / Figma Make setup guide alongside the other clients. Connect it to https://mcp.edworking.com/mcp after deploying the matching API and MCP changes.
The AI connector and the UI plugin are independent clients of this server. The AI uses the existing create_task and create_doc tools; it does not need the plugin running. Enable writing in the client and aut
只显示了开头部分;其余内容请在仓库中阅读