# Connect Typenode to Claude

Add the Typenode MCP connector to Claude, so Claude can build and run workflows in your workspace.

Claude connects to Typenode through the Typenode MCP connector. Once connected, Claude works in one Typenode workspace as you: it can do what you can do there, and never more.

You need a Typenode account in a workspace that isn't view-only.

> [!NOTE]
> Typenode is in review for Claude's directory
> Until Claude lists it, connect Typenode as a custom connector, as shown below.

## Add Typenode as a custom connector

This works in Claude on the web and in the desktop app.

1. [Open Claude with Typenode filled in](https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Typenode&connectorUrl=https%3A%2F%2Fmcp.typenode.ai%2Fmcp).
2. Click **Add**, then **Connect** next to Typenode.
3. On the Typenode page that opens, confirm it was you and click **Allow**.

To add it by hand, name the connector **Typenode** and use this URL:

```text
https://mcp.typenode.ai/mcp
```

You can also start from Typenode: on **Home**, click **Connect** and choose **Claude**.

## Connect Claude Code

Run this in your terminal. It adds Typenode to Claude Code for all your projects, then opens the Typenode page in your browser.

```shell
claude mcp add --transport http --scope user typenode https://mcp.typenode.ai/mcp; claude mcp login typenode
```

On the Typenode page, confirm it was you and click **Allow**.

## What Claude can do

Claude uses Typenode's tools to work in your workspace. It can:

- build workflows, change their steps, and deploy them
- add triggers (webhooks, emails and schedules) and turn them on or off
- read runs and the output of each step, and resume a run that is waiting
- connect accounts as credentials, and manage environments, variables and secrets
- start a workflow from a template
- publish workflows as MCP connectors
- manage roles, access keys and who can reach what, and show who changed what
- read and save skills, the playbooks Claude follows to build or debug

Claude only gets the tools your role allows. Deleting something takes two steps: Typenode first shows what would change, and acts only once you confirm.

Deploying a workflow, turning on a trigger or resuming a run can start its steps, including the ones that write to other apps.

> [!TIP]
> Secrets never go through the chat
> When a step needs a password, an API key or an account connection, Claude gives you a link to a Typenode page where you enter it.

## Example prompts

- "List my workflows and tell me which ones haven't run this week."
- "Why did the last run of my Invoice sync workflow fail? Show me the step that failed and its output."
- "Add a webhook trigger to my Lead intake workflow and give me its URL."
- "Which templates could I start from to handle new orders?"
- "Who last changed my Invoice sync workflow, and what did they change?"

## Common problems

### Claude asks you to connect again

An agent stops working after 30 days without use. Connect Typenode again from Claude's connectors. The Typenode page offers to reconnect your agent with its old name, or to add a new one.

### The Typenode page says the workspace is view-only

A view-only workspace can't connect agents until an Owner picks a plan. Ask an Owner of the workspace to pick one in **Billing**.

### Claude says the workspace is view-only or has no credits

Claude stays connected and can still read everything. In a view-only workspace, changes wait until an Owner picks a plan in **Billing**. With no execution credits left, new runs wait until someone buys an execution pack in **Billing**; editing keeps working.

### You've reached the limit of agents

You can keep 10 agents for each app in a workspace. On Typenode's **Home**, disconnect one you no longer use, then connect again.

### A tool is missing, or Claude says it isn't allowed

Claude sees only the tools your role and your workspace allow. An Owner can change your role.

### Claude says it sent too many requests

Wait a minute and try again.

## Privacy

Claude reaches Typenode only through the agent you approved, and you can disconnect it at any time. [Authentication](/mcp/authentication) explains what you approve and how to disconnect. Typenode's [privacy policy](https://typenode.ai/legal/privacy-policy) describes how Typenode handles your data.