WeMachines

npx add-mcp 'https://app.wemachines.com/api/mcp'

Download for macOS for Windows for LinuxSign up

WeMachines

Features Pricing News Changelog Startups

Theme

Download for macOS for Windows for LinuxSign up Log in

Connect your AI tools to WeMachines

WeMachines runs an MCP server, so Claude, ChatGPT, Codex, Cursor and other AI tools can work with your team’s tasks, docs and chat. You log in once, pick a workspace, and choose whether the tool may make changes.

The address

Every client connects to the same address:

https://app.wemachines.com/api/mcp

Copy

It speaks Streamable HTTP and logs in with OAuth. There is no key to copy: your client opens a WeMachines page where you log in and approve. The server is free on every plan, and the AI runs on the plan you already have with your client.

Set up your client

Claude

In Claude, open Settings, then Connectors, and add a custom connector with the address above. On a Team or Enterprise plan, an owner adds it for the organization first. Claude opens WeMachines to log in the first time you use it.

Claude Code

$claude mcp add --transport http --scope user wemachines https://app.wemachines.com/api/mcp

Copy

Then run /mcp, pick wemachines and log in. To set up a whole repository for the team, with the workflow file and the guard that keeps writes inside it, run the installer in the repository instead:

$curl -fsSL https://wemachines.com/install | sh

Copy

ChatGPT

Add WeMachines as an app in ChatGPT’s settings, under Apps, with the address above. Custom apps depend on your ChatGPT plan and your workspace admin’s settings.

Codex

$codex mcp add wemachines --url https://app.wemachines.com/api/mcp

Copy

Then log in:

$codex mcp login wemachines

Copy

Cursor

Add WeMachines to Cursor, or put this in ~/.cursor/mcp.json:

{ "mcpServers": { "wemachines": { "url": "https://app.wemachines.com/api/mcp" } } }

Copy

VS Code

$code --add-mcp '{"name":"wemachines","type":"http","url":"https://app.wemachines.com/api/mcp"}'

Copy

Anything else

Any client that supports remote MCP servers with OAuth works: Windsurf, Zed, JetBrains and the rest. Give it the address and log in when it asks.

What it can do

It reads:

Workspace and people

Which workspace you are in, its members and their roles.

Tasks

List, filter and read tasks with their full body and comments.

Docs

List and read the pages in the team’s library.

Chat

Recent messages in the team’s rooms, and past huddles with their notes.

Apps

What each of the team’s apps holds, in a few lines.

Calendar

Events, and a time that suits everyone (when Google Calendar is connected).

Routines

The standing jobs the team’s machines run, and their history.

Organization

Other teams in your organization, when you are in one.

Everything else

Labels, statuses, repositories, code, memory and research, by name.

And, when you allow it, it writes:

Tasks

Create a task, change it, or move it to another status.

Live work

Show the team you are on a task, and say what changed when you stop.

Docs

Write a new page or edit one in place.

Chat

Post a message, a comment or a poll, marked as sent for you.

Calendar

Create, move or cancel an event.

Routines

Set up a job one of the team’s machines runs on a schedule.

Machines

Ask one of the team’s machines for help, or start a coding run on a task.

Every tool says whether it only reads, and whether a change can’t simply be added back, so your client knows which calls to confirm with you first.

How access works

• You choose the workspace. A connection reaches the one workspace you pick when you log in, and only what you can already see there.
• You choose read only or read and write. Read only is enforced by the server on every call, whatever the client does. Viewers are always read only.
• It acts as you. Tasks and pages it writes carry your name. Chat messages, comments and polls are posted by your machine and marked as sent for you, so the team can tell them from your own words.
• Access follows your membership. It is checked on every call, so when you leave a workspace or are removed, the connection stops working at once. Disconnect it in your client at any time.
• Mail stays yours. Gmail never goes through this server. Where Outlook is connected, a client can reach only your own mailbox, never a teammate’s.

Your data

What a tool returns goes to the AI client you connected, under that client’s own terms. WeMachines records when a client is connected, and what it changes shows in the workspace like any other change. It receives what each tool call asks for, never your conversation with the client. The privacy policy covers what we store and for how long, and the security page how we protect it.

If it doesn’t connect

• It asks you to log in again. Access renews on its own while you use the client. After 30 days without use, log in again.
• It finds no workspace. Make one at app.wemachines.com, then connect again.
• Writes are refused. The connection was approved as read only, or you are a viewer in that workspace. Connect again and choose read and write.

Questions or a problem? See support, or write to shorn@wemachines.com.

[{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"WeMachines","item":"https://wemachines.com"},{"@type":"ListItem","position":2,"name":"MCP server","item":"https://wemachines.com/mcp"}]},{"@context":"https://schema.org","@type":"TechArticle","headline":"Connect your AI tools to WeMachines","url":"https://wemachines.com/mcp","description":"How to connect Claude, ChatGPT, Codex, Cursor and VS Code to the WeMachines MCP server, what it can read and write, and how access works.","publisher":{"@id":"https://wemachines.com/#organization"}}]