Connect a service

Point Tallgeese at an online service's MCP address.

Connect a service

Many services now offer an MCP address, a web address that lets assistants work inside them. If the service you love has one, you don't build anything. You write the address in item.toml, people sign in to the service in their browser, and Tallgeese can use whatever the service offers.

[[provides]]
kind = "remoteServer"
server = "sample-wiki"
url = "https://wiki.example/mcp"
auth = "oauth"
tools = { only = ["search", "read_page", "write_page"], ask = ["write_page"] }

# Optional: instructions written for that service, behind the same switch
[[provides]]
kind = "skillPack"
skills = ["wiki-meeting-notes"]

Choices to make

• auth: "oauth" if people sign in with the service's own login page, otherwise "none". The address must start with https://.
• only: the abilities you want to offer. Some services list hundreds, which would overwhelm the assistant. Pick the ones people actually need.
• ask: abilities that always ask permission first. Anything that sends, deletes, changes or spends should be here.
• Read-only is a perfectly good choice. If a service can't separate safe actions from risky ones, offer only the safe ones.

Will sign-in work?

Tallgeese introduces itself to the service by name and the person approves in their browser. This works with services that welcome new apps. It doesn't yet work with services that require every app to be pre-registered with them first, or that insist on a private secret. Check the service's developer documentation before you start.

Add skills for the service

A service's tools work much better with a skill that explains how to use them well, such as which to call first and how to format results. Put the skill beside the connector so one switch covers both. If you adapt someone else's instructions, keep their licence file and say what you changed.