RoutineOSBeta
Learn

Claude MCP: connect a server in one line, with a free one to try.

MCP is a standard way for Claude to use another service, such as a docs library, a mailbox or a code host. A Claude MCP server is the service on the other end. This guide explains what that means in plain words, how to add one in Claude Code or on claude.ai, and uses the free, read-only RoutineOS docs server as the worked example.

Get startedAdd the docs MCP
Free, no sign infrom the docs
What it is

What is an MCP server?

MCP stands for Model Context Protocol. It is a shared language that lets Claude call tools and read information that live outside the chat. A server is any service that speaks it. Once Claude is connected, it can use that server's tools while it works with you, instead of guessing.

On claude.ai, a connector is one way of adding an MCP server. In Claude Code you add one from the command line. The connectors guide covers how connectors behave in scheduled runs and how RoutineOS gates every write.

A free example

Add the free RoutineOS docs MCP server

The RoutineOS docs and template catalog are a free MCP server. It needs no account and no sign in, and every tool is read only. It is a safe first server to try.

  1. In Claude Code, run one linePaste this in your terminal. If you install the RoutineOS plugin, it connects the server for you.
claude mcp add --transport http routineos https://docs.routineos.org/api/mcp
  1. Or add it on claude.aiIn Claude on the web or Claude Desktop, open Customize, then Connectors, then + Add and Add custom connector. Name it RoutineOS, paste https://docs.routineos.org/api/mcp, choose No sign in, then Add. Turn it on in a chat from + > Connectors.
  2. Share it with the projectAdd --scope project to the command above and the server is written to the repository's .mcp.json. Everyone on the repo gets it, and so do cloud scheduled routines on that repo.
  3. Ask Claude somethingFor example, "search the RoutineOS docs for gates", or "set up the jobs watch template".

Source: the RoutineOS README and The RoutineOS MCP. Free plans allow one custom connector. On Team and Enterprise an owner adds it under Organization settings, Connectors.

Project scope

Why the project scope matters for scheduled runs

A cloud scheduled task sees connectors from your claude.ai account and a .mcp.json committed to its repository. It does not see servers you added on your own machine with plain claude mcp add. If a routine should use a server, add it as a connector or commit it with the project scope.

A server added on a laptop also cannot be a claude.ai connector, because a custom connector has to be reachable over the public internet.

Docs-stated. Source: The RoutineOS MCP, which cites Anthropic's scheduled tasks and custom connector documentation.

What it gives Claude

What the docs MCP can do, and what it never does

Nine tools

  • Read: search the docs, get a page, list pages.
  • Templates: list the catalog, get a template, return the steps to install one.
  • Start: how to install the plugin.
  • n8n: search the public n8n gallery and return the migrate steps for a workflow.

It never

  • Runs a command or writes a file. It only returns text.
  • Installs anything. It returns the steps for your Claude to run, after you agree.
  • Asks for an account or stores who uses it.

Source: The RoutineOS MCP. Only the two n8n tools make outbound requests, to the public n8n template gallery. RoutineOS is not affiliated with n8n.

Connect it, then build a routine

Install the plugin in Claude Code and start from a template. Free (MIT). Needs a paid Claude plan.

Get startedRead about connectors