Let agents use tools.
Stay in control of what they do.

Governance first, then everything else

How Matimo is different

Most agent tooling stops at "here are functions to call". Matimo adds the checks before a call and the record after it, and keeps both in your hands.

These are general categories, not named products. Why Matimo also lists what Matimo does not do, including compliance certifications, which it has none of.

Build your own tools and MCP server

Enterprises rarely need only public APIs. Matimo is built for your internal ones: define the tool, set the rules, expose it over MCP, and keep the evidence.

# tools/crm_lookup_customer/definition.yaml
name: crm_lookup_customer
version: "1.0.0"
description: Look up a customer in the internal CRM
parameters:
  customer_id:
    type: string
    description: The customer ID
    required: true
execution:
  type: http
  method: GET
  url: https://crm.internal.example.com/api/customers/{customer_id}
  headers:
    Authorization: Bearer {CRM_API_TOKEN}

# policy.yaml (fields are listed in the policy reference)
allowedDomains:
  - crm.internal.example.com
allowedHttpMethods:
  - GET
  - POST

# stdio for Claude Desktop or Cursor, with your own tools
npx matimo mcp --tool-paths ./tools

# a shared server with TLS and Vault-backed secrets
npx matimo mcp --transport http \
  --cert cert.pem --key key.pem \
  --secrets vault --tool-paths ./tools

What stays under your control

• Private tool directories, or your own @yourco/* provider package
• Allow and deny lists for what the MCP server exposes
• Bearer token and TLS for the HTTP transport
• Secrets from environment, .env, Vault or AWS Secrets Manager
• Credentials injected at call time through {NAME} placeholders
• An audit file you own, with no vendor in the call path

Package your own tools →MCP server guide →Policy reference →

Ready-made tools, and room for your own

129 provider tools in 10 packages, plus 449 governed Composio tools in TypeScript. Add your own in a YAML file.

• Slack
• GitHub
• Gmail
• Microsoft
• Notion
• PostgreSQL
• HubSpot
• Mailchimp
• Twilio
• Bruno
• Your own tools

Works everywhere

Deploy to any framework or agent runtime without rewriting a tool.

Complete feature set

Everything needed to run agent tools in production.

Why teams choose Matimo

Four integration patterns

Pick what fits. Each pattern is shown in both SDKs.

matimo = await Matimo.init(auto_discover=True)
result = await matimo.execute('tool-name', params)

const matimo = await MatimoInstance.init({ autoDiscover: true });
await matimo.execute('tool-name', params);

class Agent:
    @tool('tool-name')
    async def my_method(self, param):
        pass  # executed through Matimo

class Agent {
  @tool('tool-name')
  async myMethod(param: string) {
    // executed through Matimo
  }
}

from matimo import convert_tools_to_langchain
tools = convert_tools_to_langchain(matimo.list_tools(), matimo)

import { convertToolsToLangChain } from '@matimo/core';
const tools = await convertToolsToLangChain(matimo.listTools(), matimo);

from matimo.mcp.server import MCPServer, MCPServerOptions

server = MCPServer(matimo, MCPServerOptions(transport="stdio"))
await server.start()

# stdio (Claude Desktop)
npx matimo mcp
# HTTP (remote agents)
npx matimo mcp --transport http

Developer CLI

Environment setup, validation and approval workflows from the terminal. Run it with npx matimo or, in Python, matimo.

Quick start resources

Production ready