For agents

Connect the AI tools you already use. Same account, same rules.

Wavn is a remote MCP server as well as a workspace. An AI tool you already use - Claude, Claude Code, Cursor, or an agent you built - can connect and work through Wavn on your behalf: talk a decision through, order a build, fetch the finished file. This page is the whole setup.

The address

https://my.wavn.app/api/mcp

Claude Code

claude mcp add --transport http wavn https://my.wavn.app/api/mcp

Cursor

In .cursor/mcp.json, for one project, or the same file under your home folder for every project:

{ "mcpServers": { "wavn": { "url": "https://my.wavn.app/api/mcp" } } }

Claude, on the desktop or the web

Customize, then Connectors, then Add custom connector. Paste the address. There is no file to edit for a remote server.

Streamable HTTP, and two ways in:

Sign in

Point any MCP client at the address. It finds /.well-known for itself, registers itself, and requests consent from a signed-in person, once. No key to copy.

Or a key in the address

A signed-in person mints a key in the app - Connections, under Work - and the URL includes the key, so one paste connects the tool. No header to type, no field to guess:

https://my.wavn.app/api/mcp/<your key>

The tools

Every tool the server offers, in the order it lists them. A plan is a numbered list of points the person answers inside the app; a call is a decision locked with its reasons.

ask_wavn

You say anything, as you would in the app; Wavn decides for itself whether it is a build, a schedule instruction or a conversation, and answers.

build

You order one file made. It returns a task id to poll.

get_build

It reports where one build got to: what it is doing, what it produced, or what went wrong.

list_builds

It lists recent builds on the account, newest first, with their state.

get_file

It brings a built file back: text inline, anything else as a link that works for seven days.

list_projects

It lists the projects on the account, most recently touched first, with what each holds.

list_schedule

It lists what is on the schedule, each item with where it came from.

add_schedule_item

It puts something on the schedule at a known time.

read_chat

It reads recent turns of a conversation back, to pick up where it left off.

create_pipeline

It creates a plan: numbered points the person answers inside the app, each with its own thread.

add_points

It grows a plan that already exists instead of starting another.

refile_plan

It moves a plan under another plan, or lifts it out to stand on its own.

list_pipelines

It lists the plans on the account: title, state, and how many points are done.

get_pipeline

It reads one plan whole: every point with its status, its body and its thread.

get_point

It reads one point of a plan from its tracking code: the instruction, the thread and the files the work is about.

pipeline_reply

It reports into a point’s thread, signed as the connected tool, never as the person.

set_point_status

It moves one point of a plan to open, doing, done or blocked.

check_overlap

It asks whether two pieces of open work on the account are the same job. It warns, never blocks.

teach_project

It writes something into a project’s memory, and every chat in that project grounds on it from the next answer.

claim_places

It says which files a session is about to work in, and learns whether another session is already there.

release_places

It lets go of the places a session was holding.

decide

It locks a call from the conversation: the question, the call, what was argued against it and what is still open.

confirm_call

It stands behind a locked call, which opens the brief.

settle_call

It says how a locked call turned out, after time has passed: held, wrong, changed or withdrawn.

write_brief

It writes the brief for a confirmed call: the whole job in plain words, in build order.

make_plan_from_brief

It turns a brief into a plan, its pieces becoming the points in order.

share_link

It hands out the booking link: the account’s own booking address, or one meeting’s.

offer_times

It lists the open times for a meeting, read as the booking page reads them.

book_time

It books one of the open times for somebody, as Book It on the booking page does.

The rules do not change at this door.

The same allowance

A connected tool gets exactly what the person gets: the same builds, the same allowance, the same refusals. Builds count against the account's monthly allowance, and a refusal says exactly why. There is nothing to work around.

Nothing is pushed

A build returns a task id. The agent polls get_build, and get_file brings the file back when it is done. Nothing arrives on its own.

Honest failure

A build that fails hands over the partial work, the sources it found, and the wall it hit, named. An agent is never told a job succeeded when it did not.

The person holds the key

Every connection is switched on by a signed-in person and can be closed by one. Disconnecting kills every token the tool holds, on its next call. Everything it ever made stays.

Connect a tool in a minute.

Sign up is free with no card. The MCP door is on every plan, including Free.