Agent Integrations

Agent Integrations let your organisation add external tools to Ru. You can connect a remote MCP server or describe fixed operations on an HTTP API.

Only organisation administrators and owners can manage integrations. Other users can use enabled tools through Ru when their normal Runnit access allows the underlying action.

Note

Runnit’s hosted setup already includes the built-in scrape_url and crawl_website tools. These use the bundled Crawl4AI service. You don’t need to register Crawl4AI again unless you want to connect a different server or expose separately named operations.

Connect a system from the connector catalog

The fastest path for well known systems. The catalog lists over one hundred enterprise systems whose vendors publish an official MCP server, from Slack, Jira, and Notion to Xero, Salesforce, and NetSuite, grouped by category with a search box. The current public list is at runnit.io/integrations, and each connector has its own page in the connector catalogue covering exactly what it needs to connect.

1. Open Admin > Agent Integrations.
2. Select Browse connectors and pick your system.
3. Fill in what the connector asks for. Depending on the system this is an OAuth sign-in with the vendor, an API key or token, a service account, or the server URL from your vendor’s admin console. The form explains where each value comes from, and lists any plan or licence the vendor requires. Some vendors need extra values, such as a region or a tenant identifier, and the form asks for exactly those.
4. Some systems connect with a personal sign-in. For those, Runnit asks you to confirm that agents will act in that system as the account you connect. Where possible, sign in with a dedicated service account rather than a personal one. The connected account is shown on the integration card so it is always clear whose access agents are using.
5. Select Connect. For an OAuth connector, your browser goes to the vendor to approve access and returns to Runnit to finish. The approval must finish in the same browser it started in.

Runnit discovers the connector’s tools and shows them on the integration card.

What the catalog badges mean

• Verified: Runnit has connected to this system end to end and exercised it, with the connection path named. Verification is repeated over time and whenever the vendor changes its server.
• Available: connectable today through the vendor’s official MCP server, using the same open standard, but not yet through Runnit’s own end to end check.
• Listed: the vendor ships an MCP server that cannot be connected from Runnit yet. The card states the reason, for example a vendor restriction or a connector registration still in progress.

How catalog integrations differ from custom ones

A catalog integration’s server address and authentication method come from the connector definition, not from a form, so they cannot be edited afterwards. You can rename the integration, enable or disable it, change its availability to agents, and rotate a token or API key. To change anything else, delete the integration and connect again. This is what makes the Verified badge trustworthy: a verified connector is always talking to the endpoint that was verified.

When a connection expires

If a vendor later invalidates the connection, the integration card shows Reconnect needed and its tools are withheld from agents until an administrator selects Reconnect and approves access with the vendor again. Reconnecting reuses the details already on the integration; you do not need to re-enter them. This is different from a temporary outage, where Runnit keeps the last known tools and simply shows the latest connection error.

Add any other remote MCP server

Systems that are not in the catalog can still be connected, as long as they expose a remote MCP server with a tool list.

1. Open Admin > Agent Integrations.
2. Select Add integration.
3. Enter a clear Name. Check the generated Slug, which becomes part of each tool name.
4. Set Type to Remote MCP server.
5. Enter the full MCP Base URL.
6. Choose Authentication. You can use no authentication, a bearer token, or an API key header.
7. Enter the credential when authentication is required. For an API key header, also enter the header name expected by the server.
8. Keep Enabled selected to make the integration active.
9. Keep Available to Ru and all agents selected so Ru receives the tools.
10. Select Add integration.

Runnit connects to the server and discovers its available tools. A healthy integration shows the namespaced tool names that Ru receives, for example ext_research__search.

Add an HTTP API

HTTP API integrations expose a fixed set of operations. Ru can’t change the base URL, request method, or path while it runs.

1. Open Admin > Agent Integrations and select Add integration.
2. Set Type to HTTP API.
3. Complete the name, slug, base URL, authentication, and availability fields.
4. In HTTP tool definitions (JSON), add one object for each operation.
5. Select Add integration.

Each operation needs a name, description, HTTP method, relative path, and JSON input schema. For example:

[
  {
    "name": "scrape_url",
    "description": "Scrape a public URL and return clean page content.",
    "method": "POST",
    "path": "/md",
    "inputSchema": {
      "type": "object",
      "properties": {
        "url": {
          "type": "string",
          "description": "Public URL to scrape."
        }
      },
      "required": ["url"],
      "additionalProperties": true
    }
  }
]

For GET and DELETE, Runnit sends tool arguments as query parameters. For POST, PUT, and PATCH, it sends them as a JSON body.

Caution

Only connect services you trust. The description and input schema tell the assistant when and how to call the service. Make them specific, and don’t put passwords, API keys, or tokens in the URL or JSON definition. Use the credential field instead.

Test and manage an integration

The integration card shows its status, exposed tools, availability, and a masked credential hint.

• Select Test to reconnect to an MCP server and refresh its tools. For an HTTP API, this validates the configured tool definitions. The actual endpoint is checked when Ru calls it.
• Select the edit button to change the endpoint, availability, authentication, or tool definitions. Leave the credential blank to keep the current one. Changing authentication to None removes the stored credential.
• Clear Enabled to remove its tools from new runs without deleting the configuration.
• Delete the integration to remove its tools permanently.

If an MCP server is temporarily unavailable, Runnit keeps the last successfully discovered tool list and shows the latest connection error. Fix the endpoint or credential, then select Test again.

Control availability

Available to Ru and all agents is selected by default. This makes the tools available to Ru everywhere it runs, including background Ru tasks. Clearing it keeps the integration configured but withholds its tools from Ru, which is useful while you set up or test an endpoint.

See AI Directives for steering how Ru uses its tools, and AI Usage & Model Settings for usage reporting.