Toolkit API Overview

Looking for the product view?

The Help Center explains this surface as users see it: Working with Toolkits.

The Informer Toolkit API provides endpoints for managing AI toolkits that extend assistant capabilities through external tools and integrations. All routes are prefixed with /api.

Features

• CRUD Operations - Create, read, update, and delete toolkits
• Tool Management - Add and configure individual tools
• MCP Integration - Model Context Protocol support for remote tools
• Discovery - Automatic tool discovery from MCP servers
• Configuration Parsing - Normalize various MCP config formats
• Chat Associations - Enable/disable toolkits for specific chats
• Drivers & Templates - Toolkit type management
• Sharing - Control access with team-based permissions

Toolkit Types

Type	Description
mcp-stdio	MCP server running as local subprocess
mcp-remote	MCP server accessed via HTTP/SSE
informer	Built-in Informer tools
custom	Custom user-defined tools

Authentication

All Toolkit API endpoints require:

• Valid session or API token
• AI entitlement verification (for most operations)
• Write permission for modification operations

Common Permission Patterns

Operation	Permission Required
Create	toolkits:create
Read	AI access (read access implicit)
Update	toolkit:write
Delete	toolkit:delete
Share	toolkit:share

Model Context Protocol (MCP)

MCP is a standard protocol for connecting AI assistants to external tools and data sources.

MCP Server Types

• stdio - Local process communication via stdin/stdout
• remote - HTTP/SSE-based remote servers
• sse - Server-Sent Events for streaming

Configuration Formats

The toolkit API normalizes various MCP configuration formats:

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/dir"]
    }
  }
}

Tool Discovery

For MCP toolkits, tools can be automatically discovered:

1. Parse Config - Normalize MCP server configuration
2. Discover Tools - Query MCP server for available tools
3. Store Tools - Save discovered tools to toolkit

Chat Integration

Toolkits can be enabled for specific chats:

• Chat-Toolkit Association - Link toolkit to chat
• Tool Availability - Tools from enabled toolkits are available in chat
• Dynamic Enabling - Toggle toolkits on/off per chat

Error Responses

Standard HTTP status codes:

• 200 - Success
• 201 - Created
• 400 - Bad request (validation error)
• 403 - Forbidden (insufficient permissions)
• 404 - Resource not found
• 500 - Internal server error

Next Steps

Explore the specific endpoint categories:

• Core CRUD - Basic toolkit operations
• Tools - Tool management
• MCP Integration - MCP discovery and configuration
• Chat Associations - Enable toolkits in chats
• Sharing - Access control