Download Mobile AppFind the work
Browse projects, statuses and tasks. Search recent task titles and open the matching task with a source link.
list_projectslist_project_statuseslist_tasksget_tasksearchfetchOfficial MCP server
Your Workspace. In Your AI Assistant.
Connect Edworking to ChatGPT, Claude, Codex and other MCP clients. Get context from your tasks and conversations, then take the next step with the permissions you choose.
Remote MCP · OAuth · Open source
- 01
Your AI assistant
- 02
Edworking MCP
- 03
Your workspace
From a question to progress
Your assistant discovers the tools on Edworking MCP. When you ask it to act, the server checks your connection and permissions, calls Edworking, and returns the result. Your workspace stays the source of truth.
One URL. Your choice of assistant.
Use Streamable HTTP with OAuth. You need an Edworking account with access to API tokens and permission to add a custom MCP server in your assistant.
- Add the server URL in your assistant and start its OAuth connection.
- In Edworking, open Profile → API tokens. Create a dedicated token for this assistant and workspace with the requested permissions.
- Paste that token only into the Edworking MCP browser authorization page. Review the client, destination and permissions, then approve.
Never paste tokens into a chat or client configuration. The hosted server gives your assistant a separate OAuth credential. Native one-click Edworking sign-in is not available yet.
Set up your assistant
Configuration guides for the clients below. Streamable HTTP, discovery and OAuth are tested at the protocol level; real-account testing in each client is still pending. Availability depends on the client version, plan and administrator settings. These guides do not imply a directory listing or partner endorsement.
ChatGPT
In ChatGPT Plugins, use + → Add custom MCP server. Enter Edworking MCP, the server URL and OAuth authentication. Review the connection and create the plugin. Install it and enable it in a new conversation. Edworking MCP is not yet published in the public directory.
Client documentation ↗Codex
Run these commands in your terminal, then complete the browser connection.
codex mcp add edworking --url https://mcp.edworking.com/mcp
codex mcp login edworkingClaude
In Claude Settings → Connectors, add a custom connector with the server URL. Complete the browser authorization and enable the connector in your conversation. If your desktop client only supports local servers, see the bridge option below.
Client documentation ↗Claude Code
Run the command, then open Claude Code and use /mcp to finish authorization.
claude mcp add --transport http edworking https://mcp.edworking.com/mcpCursor
Merge this entry into your MCP configuration, keeping any existing servers. Start the server and complete OAuth in your browser.
.cursor/mcp.json
{
"mcpServers": {
"edworking": {
"url": "https://mcp.edworking.com/mcp"
}
}
}VS Code / GitHub Copilot
Merge this entry into your MCP configuration, keeping any existing servers. Start the server and complete OAuth in your browser.
.vscode/mcp.json
{
"servers": {
"edworking": {
"type": "http",
"url": "https://mcp.edworking.com/mcp"
}
}
}Windsurf
Merge this entry into your MCP configuration, keeping any existing servers. Start the server and complete OAuth in your browser.
~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"edworking": {
"serverUrl": "https://mcp.edworking.com/mcp"
}
}
}Devin
In Settings → MCP Marketplace, add your own MCP server. Use HTTP transport, the server URL and OAuth authentication. Enable it, then follow the authorization link.
Client documentation ↗Microsoft Copilot Studio
In your agent, use Tools → Add tool → New tool → Model Context Protocol. Enter the server URL, select OAuth and Dynamic Discovery (DCR). Create and authorize the connection. Tenant policies and public-client OAuth compatibility need validation.
Client documentation ↗Google Antigravity
Merge this entry into your MCP configuration, keeping any existing servers. Start the server and complete OAuth in your browser.
mcp_config.json
{
"mcpServers": {
"edworking": {
"serverUrl": "https://mcp.edworking.com/mcp"
}
}
}Other MCP clients
For clients that support only local stdio servers, use the community mcp-remote bridge shown below. It requires Node.js and runs third-party software locally. Native HTTP is preferred. Custom clients need Streamable HTTP, OAuth discovery, PKCE S256 and resource indicators.
npx -y mcp-remote https://mcp.edworking.com/mcpWhat you can do today
15 tools, limited to the connected workspace and your existing Edworking access. Writes also require the relevant OAuth and API-token permissions.
Move tasks forward
Create projects and tasks. New tasks can include a description, deadline, initial status and existing attachments. Update an existing task’s name or deadline.
create_projectcreate_taskupdate_taskKeep the conversation moving
List private conversations, read messages in accessible conversations, and send a message to a specific conversation when requested.
list_conversationsread_messagessend_messageFiles and connection control
List file metadata, import a public HTTPS file into a project or task, and inspect your connection permissions and expiry.
list_filesupload_fileget_connectionTry these requests
- “List the tasks in my launch project.”
- “Read the latest messages in the planning conversation and summarize the decisions.”
- “Create a task in my launch project to review the proposal, due Friday.”
Know the boundaries
- Search checks titles in up to 500 recently updated tasks and returns up to 50 matches. It does not search all historical work, document bodies or message content.
- Status changes on existing tasks, reassignment, document editing, time tracking, tags, dependencies, bulk actions and deletion are not exposed by this MCP server.
- File imports use a public HTTPS URL, with an upstream limit of 50 MiB and 30 seconds. File reads return metadata, not file contents.
- The hosted MCP endpoint currently allows 120 requests per minute per source IP, shared by users behind the same network. OAuth endpoints and the Edworking API have additional limits. Respect Retry-After on HTTP 429.
You choose the access
Read access is requested by default. For writes, reconnect with the relevant write scopes and a token that allows them. Access is restricted to one workspace per connection. Disconnect in your assistant and revoke the dedicated token in Edworking to stop access.
OAuth uses PKCE S256, short-lived access credentials and rotating refresh credentials. Stored Edworking tokens are encrypted. These controls reduce risk; they are not a guarantee or an independent security audit.
Questions about Edworking MCP
MCP is a protocol for connecting software. Tool descriptions explain what is possible, and prompts or skills can guide a workflow. The server runs the authorized operations and returns current Edworking data.
No. Use the Edworking-hosted endpoint. Advanced users can self-host the open-source server or run its local stdio mode. Connecting an assistant does not create a new Edworking workspace.
The default OAuth discovery requests read scopes. To write, your client must request the appropriate write scopes and your dedicated Edworking token must include them. Reconnect after changing permissions.
Check the full URL, including /mcp, and use OAuth rather than pasting your Edworking token as a bearer header. Reconnect if a token expired or was revoked. A missing scope requires new consent. For an uncertain write result, check Edworking before repeating it.
The current connection requires scoped Edworking API tokens. API access is offered on the Business plan; check your workspace’s entitlements. Your assistant may also require a paid plan or administrator approval. The server does not publish a separate MCP pricing plan.