Esta página aún no está traducida.

Add the tools your agents may use

This page is for an organization's owners and admins. You will add the tools, skills and other AI agents your instructions may use, decide which tools are allowed, and, if you want, allow nothing else.

What an integration is

An integration is something outside instruction.md that your instructions can point to. There are four kinds:

  • MCP servers and registries. An MCP server gives an AI tools to use, such as reading a calendar, searching a database or sending a message. (MCP is the common way AI apps reach tools.) A registry is a list of MCP servers, added whole.
  • Skills. A skill is a short guide an AI follows for one kind of task. You add them from a GitHub repository.
  • APIs. An API is a web service, such as a CRM, a ticket system or a payment provider. You add it from its OpenAPI document, a file that describes what the service can do.
  • Agents. Other AI agents your instructions can hand work to, such as a support agent or a travel agent.

Once you add one, writers in your organization see it as they write. When they type & or @, the editor offers your integrations and their tools, so they pick the exact one instead of typing its address. See Mention people, tools and other instructions.

You also decide what agents may use. You can block single tools, and you can let instructions use only what you added.

People directories live in the same place, under Directories. They are explained on Bring in your company's people.

Before you start

Plans On Pro, Team, and Enterprise

  • Your role. Only the organization's owners and admins add, pull again and remove integrations. Everyone else sees what was added, and a line such as Owners and admins add servers. See Invite people and choose their roles.
  • Your plan. If your plan doesn't include integrations, the pages show Pro and above with See plans, and nothing can be added.
  • The address. You need the address its makers give you. It starts with https://.

Find the integrations pages

In the editor's side bar, open Integrations. Its first page, Overview, lists each kind under What's connected, with how many you added. Each kind has its own page:

  • Integrations ▸ Agents
  • Integrations ▸ MCP (registries first, then servers)
  • Integrations ▸ Skills
  • Integrations ▸ APIs
  • Integrations ▸ Directories

The Overview page also has Rules, where you turn on Only approved integrations.

Integrations ▸ MCP, with a server's tools open.

Add an MCP server or a registry

  1. Open Integrations ▸ MCP

    The page has two parts, Registries and Servers. Each has its own field.

  2. Paste the address

    For a server, paste the address in Add server: the server's address, as its makers give it. For a registry, paste it in Add registry.

  3. Press Add

    You see Added its name: pulling what it describes. The row shows Pulling…, then Ready with what was found, such as 12 tools · pulled just now.

instruction.md asks the server which tools it has. It does not use them. If the server asks for a sign-in, it is added but its tools aren't listed. The row says The server asks for sign-in, so its tools aren't listed.

Add skills from GitHub

  1. Open Integrations ▸ Skills

    You see the skills you added, and This server's skills: the ones instruction.md offers on its own.

  2. Paste the repository's address

    Paste the address of a GitHub repository with skills in it, such as https://github.com/owner/repository. Each skill in it is a file named SKILL.md.

  3. Choose a branch and folder (optional)

    Under Branch and folder, fill these in only if the skills aren't on the repository's main branch, or are in one folder of it. Leave them empty for the default branch and the whole repository.

  4. Press Add

    The row shows Pulling…, then Ready with how many skills were found. At most 200 skills are kept from one repository. A folder narrows what is pulled.

Add an API

instruction.md only reads the API's document. It never calls the API itself.

  1. Open Integrations ▸ APIs

    You see the APIs you added and a field to add one.

  2. Give its document

    Paste the document's address in Its OpenAPI document's address. Or press Upload file… and choose the file, in JSON or YAML. A document can be at most 5 MB.

  3. Add a token, if the address needs one (optional)

    Under Options, press Needs a token?. Paste the token in Token. If its makers say the token goes in a different header, type it in The header it goes in.

    The token is used for this one read, then forgotten. instruction.md never keeps it.

  4. Choose some operations, for a large API (optional)

    Press Only some operations? and type the tags you want, separated by commas, such as customers, tickets. Use this for an API with more than 300 operations.

  5. Press Add

    You see Added its name: 40 operations, 12 blocked until allowed, or similar.

Each operation of the API becomes a tool your instructions can name. Operations that only read are allowed. Operations that change something are blocked until an admin allows them.

Add another AI agent

  1. Open Integrations ▸ Agents

    You see the agents you added. Under them, Agents that connect lists the agents that sign in to your organization themselves. Their sign-ins are made in Developer ▸ API keys, which the side bar shows once Developer mode is on. Manage in Security opens Settings ▸ Security, where Open Developer takes you there.

  2. Paste the agent's address

    Under Add agent, paste the address of its Agent Card (a short file that describes the agent), or the address it answers at, in Its address. Its makers give you this address.

  3. Press Add

    The row shows Pulling…, then Ready. Writers can now pick the agent as they write.

Allow or block tools

Plans On Pro, Team, and Enterprise

An MCP server's tools and an API's operations can each be allowed or blocked. A blocked tool is never offered as you write. Where an instruction names one, the editor marks it.

  1. Open the server's tools

    On Integrations ▸ MCP, press Tools on the server's row. On Integrations ▸ APIs, press Operations.

  2. Decide for each tool

    Each tool shows its name and what it does, in its makers' words. Choose Allowed or Blocked. To decide for all of them at once, press Allow all or Block all.

  3. Decide for new tools

    Under New tools, choose what a tool the server adds later gets:

    • Allow: new tools may be used at once.
    • Block until reviewed: new tools wait until someone allows them.

    For an API, the row is New operations. Allow reads lets new read-only operations be used at once, and blocks the ones that change something.

The top of the list says how many are blocked, such as 3 blocked: never offered as you write, and marked where an instruction names one. A tool the server no longer lists says The server no longer lists it. It keeps your decision, in case it comes back.

Members can open the list too. They see what was decided and Owners and admins decide which tools may be used.

Allow only approved integrations

Plans On Team and Enterprise

By default, an instruction may name any server, skill or agent, even one you didn't add. Turn this on to allow only yours.

  1. Open Integrations ▸ Overview

    Find Rules.

  2. Turn on Only approved integrations

    You see Only approved integrations from now on.

From then on, instructions may use only the MCP servers, APIs, skills and agents added here. Anything else is marked as not approved, and the agent doesn't use it. Writers see a problem such as “Weather” isn't one of your organization's approved integrations, so the agent won't use it. A blocked tool shows The tool “send_email” is blocked in your organization, so the agent won't use it. Pick another tool, or ask an admin to allow it.

What a writer sees when an instruction names an integration that isn't approved.

To turn the rule off, turn the switch off again. You see Any MCP server, skill or agent may be used.

Pull again

instruction.md reads an integration when you add it, and again only when you ask. It doesn't update by itself. When a server adds tools or a repository adds skills, press Pull again on its row.

  • For an API whose address needs a token, the row asks for Its token again. It is used for this one read, never kept. Type it and press Pull.
  • For an API you uploaded, Pull again asks you to choose the file again.

If a pull fails, what was found before stays, and the row says why.

Check it worked

  • The row shows Ready, with what it found and when it was pulled.
  • In an instruction, type & or @. Your integration and its allowed tools are in the list.
  • With Only approved integrations on, a server you didn't add is marked in the editor's problems.

To see the address, branch and folder on each row, turn on Developer mode in Settings ▸ General.

Remove an integration

Press Remove on its row. The editor asks Remove its name?. Press Remove again. What it offered goes too. Instructions keep what they wrote. With Only approved integrations on, instructions that use it show it as not approved.

If it doesn't work

What you see What to do
An address starts with https:// Paste the whole address, with https:// at the start.
Didn't pull, on the row Read the line under it, which says why. Fix the address, then press Pull again.
The address asks for a token The API's document needs a sign-in. Press Needs a token?, paste a token and press Add again.
The document is larger than 5 MB Ask its makers for a smaller document, or one for only part of the API.
Kept 300 of its operations; choose tags to narrow what is pulled Remove the API, then add it again with Only some operations? and the tags you need.
No SKILL.md found Check Branch and folder. The skills may be on another branch or in a folder.
Adding it didn't work: at most 100 integrations An organization keeps at most 100 integrations, people directories included. Remove one first.

For anything else, see Something isn't working.

Questions

How do I allow only our approved MCP servers and block a tool?

Add your servers, then turn on Only approved integrations in Integrations ▸ Overview. To block a tool, press Tools on its server's row and choose Blocked. Each needs a plan that includes it. See Allow or block tools and Allow only approved integrations.

Can I add our internal API from an OpenAPI document? Does instruction.md call it?

Yes. Add the document's address, or upload the file. instruction.md reads only the document and never calls the API. A token for the document is used once and never kept.

Do writers have to type addresses by hand?

No. Once added, an integration is offered when they type & or @. Anything not added is still allowed, unless you turned on Only approved integrations, but they type its address themselves.

Does an integration update by itself?

No. It is read when you add it and when you press Pull again. Press it after the server or repository changes.

Who can add integrations?

The organization's owners and admins. Other members can see what was added and which tools are allowed.

Last checked against the product:

Was this page helpful? Report a problem