Tools
Tools let your applications call MCP servers, from preintegrated services such as Notion, GitHub or BigQuery to your own server, through a single MCP endpoint. Your organization decides which servers and tools are available, and each application reaches only the ones configured for it, identified by its application API key.
Required role
Applies to
Start with the MCP section of the Quickstart to connect a client and make your first tool call.
Why use it
Tools are where agents stop answering and start acting: they read your workspace, query your data and change records. Wired straight to each MCP server, every team keeps its own tokens and its own idea of which tools are safe, and no one can say which agent can do what. Tools puts that decision in one place and enforces it on every call.
- Connect once, use everywhere. An Organization Admin connects each server once. Every application in scope reaches it through the same MCP endpoint, so no team rebuilds the integration.
- Credentials stay out of your agents. Applications authenticate with their application API key. The server's token or OAuth sign-in stays with Optiak and is never shown again once saved.
- Least privilege, enforced at runtime. The organization allows tools and each application narrows them. The Gateway checks both lists on every list and every call, so an application can't reach a tool outside its list, even by name.
- Compliance covers tools too. Your organization's data governance rules apply to the servers applications use, not only to models, so a tool call can't take data where your policies don't allow.
- Every tool call on record. Optiak records each tool list and tool call with the application and application API key that made it, its outcome and its latency, so you can trace what every agent did.
- Standard MCP. Any MCP client that supports Streamable HTTP connects without Optiak-specific code.
How it works
Applications reach their tools through the MCP Gateway, the Gateway endpoint for the Model Context Protocol (MCP), with the same application API key they use for LLM requests. Any MCP client that supports Streamable HTTP and an Authorization: Bearer header can connect. See the Gateway overview for how it sits next to LLM requests.
How applications use tools
Configure your AI application's model connection and MCP connection separately. Send model requests to the Inference Gateway and connect the MCP client to the MCP Gateway, using the same application API key for both.
Your AI application uses an MCP client to discover the tools enabled for it and present them to the LLM. The LLM chooses a tool and its arguments; the client sends the call through Optiak. Your application then passes the result back to the LLM so it can continue answering.
Follow the MCP quickstart to test discovery and a tool call. For the protocol flow and the roles of the agent, client and server, see the official MCP architecture walkthrough.
The organization chooses, the application narrows
An Organization Admin connects each server once, chooses which of its tools are allowed and sets its scope: the whole organization, selected projects or selected applications. An admin of the application (App Admin, Project Admin or Workspace Admin; see Members and Access) then adds the server to it and keeps every allowed tool or selects a subset. Applications can narrow the organization's choice, never widen it, as in the rest of Optiak: the organization enables, the application narrows.
An application can call a tool only when all of these hold:
- The server is active in the organization.
- Its scope includes the application.
- The application has added the server and keeps it enabled.
- Both the organization's and the application's tool selection allow the tool.
- The server meets your organization's data governance rules.
- The connection to the server works.
The Gateway checks these rules every time it lists or calls tools, so changes apply to the next request.
Sources
Choose a preintegrated server from Optiak's catalog, or connect a custom MCP server using its URL. Applications use tools from either source through the same MCP endpoint.
Preintegrated servers
Preintegrated servers come ready in the catalog. Every provider has its own endpoint, sign-in method (OAuth, a service account key or an API key in a provider-specific header) and setup fields; Optiak already knows them, refreshes OAuth access where the provider allows it and discovers each server's tools for you. An Organization Admin only connects an account and picks the tools, and your applications reach every server the same way, through one MCP endpoint.
| Server | What applications can do |
|---|---|
| Notion | Search and read pages, create pages and update workspace content |
| Linear | Search and read issues, projects and documents |
| GitHub | Search and read code, issues and pull requests |
| Atlassian | Search, read, create and update Jira issues and Confluence pages |
| Slack | Search messages and files, and read channels and threads |
| BigQuery | Explore datasets, inspect table schemas and run SQL queries |
| Databricks | Query data with Genie or SQL, search AI Search indexes and run Unity Catalog functions |
| DeepWiki | Explore documentation and get answers about public GitHub repositories |
| Exa | Search the web and read web pages |
To prepare and connect each provider's account, see Connect MCP Servers.
Custom MCP Servers
To use any other MCP server, your own or a third party's, pick Custom MCP Server in the catalog and enter the server's URL.
| Requirement | Value |
|---|---|
| URL | Public HTTPS URL, including its path. Localhost and private networks are not reachable. |
| Protocol | MCP over Streamable HTTP |
| Authentication | OAuth 2.0 with PKCE and discoverable authorization/token endpoints (the server must support CIMD or DCR), an API key or token sent in a header, or no authentication |
| Discovery | The server must answer within 30 seconds and expose no more than 1,000 tools. |
For the header formats and the OAuth requirements, see Connect MCP Servers.
Set it up
An Organization Admin connects the server, then each application in its scope adds it. For who can do each step, see Members and Access.
In the organization
- In the console, open Company setup, then Tools, and click Add tools to pick a server from the catalog.
- Give the server a name and set its Data residency: where the server processes or stores data. Choose Unknown if you can't confirm it.
- Connect the server. The connection steps for each provider are in Connect MCP Servers.
- Click Discover tools and choose the Tool access: All current and future tools, or Only selected tools. Hints such as Read-only or Destructive show what the server declares about each tool.
- Choose the Scope and keep Setup active turned on.
A server with no scope, or with Setup active turned off, stays configured but exposes no tools.
In the application
In the console, open the application, then Configuration, then Tools. Add tools lists the servers whose scope includes the application. For each one, choose its Tool access: All current and future tools, so new tools the organization allows become available automatically, or Only selected tools.
Check which tools an application can reach
When you create an application API key in the application's Configuration, under Credentials, the MCP tab of the quick start shows a cURL command that lists the application's tools. It contains the key, which Optiak shows only once, so treat it as a secret. To run it from environment variables, set OPTIAK_MCP_URL to the MCP Gateway URL:
export OPTIAK_MCP_URL="https://api-mcp.optiak.dev/mcp"
curl "$OPTIAK_MCP_URL" \
-H "Authorization: Bearer $OPTIAK_API_KEY" \
-H "Accept: application/json, text/event-stream" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
- A successful response has a
result.toolslist; an empty list means no tools are available to the application yet. - If authentication fails, check that the key belongs to this application and hasn't expired or been revoked.
- If a tool is missing, go through the conditions in How it works.
Tool names end with a short suffix that keeps tools from different servers apart; call each tool by the name the list returns. To go on and call a tool, follow the MCP quickstart.
Limits and behavior
- A tool call times out after 120 seconds.
- Optiak limits how many tool discovery and execution calls an organization can run at once. A call that cannot get a slot in time returns an error asking you to retry.
- Even if one server is slow or unreachable when tools are listed, the list still includes the tools from the other servers.
- A tool result larger than the size limit returns an error instead of a truncated result.
- When you remove a server from Tools, no application can use its tools any more.
Related
- Connect MCP Servers: prepare and connect each provider's account.
- Gateway overview: where tool calls go through the Gateway.
- Members and Access: who can connect servers and enable them for applications.
- Data Governance: the organization rules that apply to tools and models.