Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 22, 15:45 UTC
Add keywords to docs pages for improved search
- Extend frontmatter schema with keywords field - Update search API to index all content sources (docs, tool-router, reference, examples, toolkits) - Add keywords to main docs pages (quickstart, tools, auth, etc.) - Add keywords to provider pages (openai, anthropic, vercel, etc.) - Add keywords to tool router pages (authentication, users, etc.) - Configure search API endpoint in layout
Sushmithamallesh committed
Jan 2, 2026 at 20:59 UTC
46a43ddadb0cca2db2a1d3110c7f632d0009f3a5
44 files changed
+82
-10
fumadocs/app/api/search/route.ts
+25
-5
@@ -1,7 +1,27 @@
1
-import { source } from '@/lib/source';
2
-import { createFromSource } from 'fumadocs-core/search/server';
1
+import {
2
+ source,
3
+ toolRouterSource,
4
+ referenceSource,
5
+ examplesSource,
6
+ toolkitsSource,
7
+} from '@/lib/source';
8
+import { createSearchAPI } from 'fumadocs-core/search/server';
9
4
-export const { GET } = createFromSource(source, {
5
- // https://docs.orama.com/docs/orama-js/supported-languages
6
- language: 'english',
10
+const allPages = [
11
+ ...source.getPages(),
12
+ ...toolRouterSource.getPages(),
13
+ ...referenceSource.getPages(),
14
+ ...examplesSource.getPages(),
15
+ ...toolkitsSource.getPages(),
16
+];
17
+
18
+export const { GET } = createSearchAPI('advanced', {
19
+ indexes: allPages.map((page) => ({
20
+ id: page.url,
21
+ title: page.data.title ?? 'Untitled',
22
+ description: page.data.description,
23
+ url: page.url,
24
+ structuredData: page.data.structuredData,
25
+ keywords: 'keywords' in page.data ? page.data.keywords : undefined,
26
+ })),
27
});
fumadocs/app/layout.tsx
+5
@@ -31,6 +31,11 @@ export default function Layout({ children }: LayoutProps<'/'>) {
31
attribute: 'class',
32
enableSystem: false,
33
}}
34
+ search={{
35
+ options: {
36
+ api: '/api/search',
37
+ },
38
+ }}
39
>
40
{children}
41
</RootProvider>
fumadocs/content/docs/authenticating-tools.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Authenticating Tools
3
description: Create auth configs and connect user accounts
4
+keywords: [oauth, api key, auth config, connect account, credentials]
5
---
6
7
The first step in authenticating your users is to create an **Auth Config**. Every toolkit has its own authentication method such as `OAuth`, `API key`, `Basic Auth`, or custom schemes.
fumadocs/content/docs/cli.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: CLI
3
description: Generate type definitions and manage authentication
4
+keywords: [command line, generate types]
5
---
6
7
The Composio CLI helps you generate type-safe code and manage your Composio workspace.
fumadocs/content/docs/connected-accounts.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Connected Accounts
3
description: Manage and monitor user connections to toolkits
4
+keywords: [list accounts, refresh token, disable, delete account]
5
---
6
7
Connected accounts are authenticated connections between your users and toolkits. After users authenticate (see [Authenticating tools](/docs/authenticating-tools)), you can manage these accounts throughout their lifecycle.
fumadocs/content/docs/custom-auth-configs.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Custom Auth Configs
3
description: Customize auth configs for any toolkit
4
+keywords: [white label, custom oauth, own developer app]
5
---
6
7
Many toolkits support a level of customization for the auth config, specifically OAuth applications.
fumadocs/content/docs/custom-auth-params.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Custom Auth Parameters
3
description: Inject custom credentials in headers or parameters
4
+keywords: [inject headers, custom credentials]
5
---
6
7
In cases where Composio is not being used for managing the auth but only for the tools, it is possible to use the `beforeExecute` hook to inject custom auth headers or parameters for a toolkit.
fumadocs/content/docs/custom-tools.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Creating Custom Tools
3
description: Learn how to extend Composio's toolkits with your own tools
4
+keywords: [create tool, custom action, extend, standalone tool]
5
---
6
7
Custom tools allow you to create your own tools that can be used with Composio.
fumadocs/content/docs/debugging-info.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Debugging Info
3
description: Share your debugging info with Composio team for faster issue resolution
4
+keywords: [debug, support, troubleshoot]
5
---
6
7
Your debugging info is tied to your project and it helps us trace what happened and debug the issue faster.
fumadocs/content/docs/executing-tools.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Executing Tools
3
description: Learn how to execute Composio tools with different providers and frameworks
4
+keywords: [execute, run, tool calling, function calling, direct execution]
5
---
6
7
LLMs on their own can only do generation. Tool calling changes that by letting them interact with external services. Instead of just drafting an email, the model can call `GMAIL_SEND_EMAIL` to actually send it. The tool's results feed back to the LLM, closing the loop so it can decide, act, observe, and adapt.
fumadocs/content/docs/fetching-tools.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Fetching tools and schemas
3
description: Fetch and filter tools, and inspect schemas
4
+keywords: [get tools, list tools, filter, schema]
5
---
6
7
Fetch specific tools, filter by permissions or search, and inspect schemas for type information. Tools are automatically formatted for your provider.
fumadocs/content/docs/index.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Welcome
3
description: Composio is the simplest way to connect AI agents to external tools and services.
4
+keywords: [getting started, introduction]
5
---
6
7
<Callout title="New: Tool Router" type="info">
fumadocs/content/docs/mcp-providers.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Providers
3
description: Connect MCP servers to AI frameworks
4
+keywords: [mcp sdk, anthropic mcp, openai mcp]
5
---
6
7
Integrate your MCP servers with popular AI SDKs and frameworks.
fumadocs/content/docs/mcp-quickstart.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Quickstart
3
description: Create your first MCP server
4
+keywords: [mcp, model context protocol]
5
---
6
7
[Model Context Protocol](https://modelcontextprotocol.io/introduction) (MCP) is an open-source standard for connecting AI applications to external tools. All the 500+ tools available in Composio are also available as MCP servers.
fumadocs/content/docs/mcp-server-management.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Server management
3
description: Create, update, and manage MCP servers
4
+keywords: [create server, update server, delete server]
5
---
6
7
This guide covers all server management operations for MCP servers.
fumadocs/content/docs/programmatic-auth-configs.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Programmatic Auth Configs
3
description: Create auth configs programmatically
4
+keywords: [create auth config, sdk]
5
---
6
7
Auth configs are created once and reused many times. However, when managing multiple toolkits, you may want to create auth configs programmatically.
fumadocs/content/docs/providers/anthropic.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Anthropic Provider
3
description: Use Composio tools with Claude
4
+keywords: [claude]
5
---
6
7
The Anthropic Provider transforms Composio tools into a format compatible with Anthropic's function calling capabilities through its Messages API.
fumadocs/content/docs/providers/crewai.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: CrewAI Provider
3
description: Use Composio tools with CrewAI agents
4
+keywords: [crew]
5
---
6
7
The CrewAI Provider formats the Composio tools into an object compatible with CrewAI's tool calling capabilities. Agents and LLM workflows built with this can call and execute the Composio tools.
fumadocs/content/docs/providers/custom-providers/index.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Custom Providers
3
description: Build your own provider for any AI framework
4
+keywords: [custom provider]
5
---
6
7
Providers transform Composio tools into the format your AI framework expects. If your framework isn't listed in our supported providers, you can build your own.
fumadocs/content/docs/providers/google.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Google Gen AI Provider
3
description: Use Composio with Gemini through the Google Gen AI SDK
4
+keywords: [gemini]
5
---
6
7
The Google provider transforms Composio tools into a format compatible with Gemini's function calling capabilities through it's API
fumadocs/content/docs/providers/langchain.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: LangChain Provider
3
description: Use Composio tools with LangChain
4
+keywords: [langgraph]
5
---
6
7
The LangChain Provider transforms Composio tools into a format compatible with LangChain's function calling capabilities.
fumadocs/content/docs/providers/llamaindex.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: LlamaIndex Provider
3
description: Use Composio tools with LlamaIndex
4
+keywords: [workflow, function agent]
5
---
6
7
The LlamaIndex Provider transforms Composio tools into a format compatible with LlamaIndex's function calling capabilities.
fumadocs/content/docs/providers/mastra.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Mastra Provider
3
description: Use Composio with Mastra's TypeScript framework
4
+keywords: [mastra]
5
---
6
7
Mastra is a TypeScript native framework for building agents with tools and MCPs. It expects tools to be in the following format:
fumadocs/content/docs/providers/openai-agents.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: OpenAI Agents Provider
3
description: Use Composio with OpenAI's Agents SDK
4
+keywords: [agents sdk]
5
---
6
7
The OpenAI Agents Provider is a provider that formats the Composio tools into an object compatible with OpenAI's Agents API.
fumadocs/content/docs/providers/openai.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: OpenAI Providers
3
description: Use Composio with OpenAI's Responses and Chat Completion APIs
4
+keywords: [gpt, responses api, chat completions]
5
---
6
7
The OpenAI Provider is the default provider for the Composio SDK. It transforms Composio tools into a format compatible with OpenAI's function calling capabilities through both the Responses and Chat Completion APIs.
fumadocs/content/docs/providers/vercel.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Vercel AI SDK Provider
3
description: Use Composio with Vercel AI SDK
4
+keywords: [ai sdk]
5
---
6
7
Vercel AI SDK allows you to configure an optional async `execute` function that the framework uses to execute the tool calls.
fumadocs/content/docs/quickstart.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Quickstart
3
description: Add composio tools to your AI agents
4
+keywords: [tutorial, setup, install, first agent]
5
---
6
7
This guide walks you through **authenticated tool calling**—the foundation of how Composio connects your AI agents to real-world actions.
fumadocs/content/docs/toolkit-versioning.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Toolkit Versioning
3
description: Pin specific tool versions for consistent behavior in production
4
+keywords: [version, pin version, tool versioning]
5
---
6
7
Toolkit versioning ensures your tools behave consistently across deployments. You can pin specific versions in production, test new releases in development, and roll back when needed.
fumadocs/content/docs/user-management.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: User Management
3
description: Manage users and their connected accounts
4
+keywords: [user id, multi-user]
5
---
6
7
## What are User IDs?
fumadocs/content/docs/using-triggers.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Using Triggers
3
description: Send payloads to your AI agents or systems based on events in apps
4
+keywords: [webhooks, events, subscribe, callback]
5
---
6
7
When events occur in connected apps (like new Slack messages or GitHub commits), triggers automatically send the event data to your application.
fumadocs/content/tool-router/authentication.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Authentication
3
description: Understand how Tool Router handles user authentication to toolkits
4
+keywords: [connect link, oauth]
5
---
6
7
Tool Router handles authentication through [Connect Links](/docs/authenticating-tools#hosted-authentication-connect-link), hosted pages where users complete OAuth or enter credentials.
fumadocs/content/tool-router/index.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Overview
3
description: Give your AI agent access to thousands of tools through a unified interface
4
+keywords: [unified interface, meta-tools]
5
---
6
7
Tool Router is a unified interface that lets an agent **search**, **plan**, **authenticate**, and **execute** actions across thousands of Composio tools.
fumadocs/content/tool-router/managing-multiple-accounts.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Managing multiple accounts
3
description: Handle users with multiple accounts for the same toolkit
4
+keywords: [multiple accounts, work personal, switch account]
5
---
6
7
Users can connect multiple accounts for the same toolkit (e.g., personal and work Gmail accounts). This is useful when users need to manage different email accounts, GitHub organizations, or separate work and personal contexts. This guide explains how to connect, select, and manage multiple accounts.
fumadocs/content/tool-router/manually-authenticating-users.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Manually authenticating users
3
description: Authenticate users to toolkits outside of chat
4
+keywords: [pre-auth, onboarding, custom ui, authorize]
5
---
6
7
Manual authentication lets you connect users to toolkits outside of the chat flow. Use this when you want to:
fumadocs/content/tool-router/migration-guide/beta-to-stable.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Beta to Stable Migration
3
description: Migrate from Tool Router beta to the stable version
4
+keywords: [upgrade, migrate, experimental, beta]
5
---
6
7
The stable version includes improved session management, multiple configuring options, and enhanced authentication capabilities.
fumadocs/content/tool-router/quickstart.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Quickstart
3
description: Build an AI agent with access to 1000+ tools
4
+keywords: [tutorial, setup, first agent]
5
---
6
7
Choose how you want to integrate Tool Router:
fumadocs/content/tool-router/tools-and-toolkits.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Tools and toolkits
3
description: Access 800+ toolkits through Tool Router
4
+keywords: [available tools, browse toolkits]
5
---
6
7
Tool Router gives your agent access to most Composio toolkits by default. For details on configuring which toolkits are available in a session, see [Users and sessions](/tool-router/users-and-sessions#enabling-toolkits).
fumadocs/content/tool-router/users-and-sessions.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Users and sessions
3
description: Understand how Tool Router scopes tools and connections per user
4
+keywords: [session, user id, enable toolkits, disable toolkits]
5
---
6
7
A **user ID** is an identifier from your system (database ID, UUID, or any unique string) that scopes connected accounts and tool access to a specific user. User IDs can represent individuals, teams, or organizations. See [User Management](/docs/user-management) for patterns.
fumadocs/content/tool-router/using-as-a-native-tool.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Using as a native tool
3
description: Use Tool Router as a native tool with any AI framework
4
+keywords: [native tool, single tool, without mcp]
5
---
6
7
Tool Router can be used as a single native tool with any AI framework. The tool handles search, authentication, and execution internally.
fumadocs/content/tool-router/using-custom-auth-configs.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Using custom auth configs
3
description: Set up auth configs for toolkits without Composio managed authentication
4
+keywords: [custom credentials, no managed auth]
5
---
6
7
Some toolkits don't have Composio managed authentication and require you to provide your own credentials. When Tool Router tries to use these toolkits, it will throw an error asking you to create an auth config.
fumadocs/content/tool-router/using-in-chat-authentication.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Using In-chat authentication
3
description: Let your agent prompt users to connect accounts during conversation
4
+keywords: [automatic auth, dynamic auth, agent prompts]
5
---
6
7
In-chat authentication lets your agent prompt users to connect accounts during chat. When a tool requires authentication, the agent returns a Connect Link URL. The user authenticates, confirms in chat, and the agent retries.
fumadocs/content/tool-router/using-with-mcp-clients.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: Using with MCP clients
3
description: Use Tool Router as an MCP server with any MCP client
4
+keywords: [mcp server, http transport]
5
---
6
7
Every Tool Router session provides a unique MCP server URL. This URL exposes the exact session you created - with the specific user, toolkits, and auth configs you configured. Any MCP client that supports HTTP transport can connect using just the URL and your API key.
fumadocs/content/tool-router/white-labeling-authentication.mdx
+1
@@ -1,6 +1,7 @@
1
---
2
title: White-labeling authentication
3
description: Use your own OAuth apps and branded auth screens
4
+keywords: [branding, own oauth, custom redirect]
5
---
6
7
White-labeling lets you use your own OAuth apps instead of Composio's. Users will see your app name on consent screens instead of "Composio".
fumadocs/source.config.ts
+11
-5
@@ -9,10 +9,16 @@ import { z } from 'zod';
9
10
// You can customise Zod schemas for frontmatter and `meta.json` here
11
// see https://fumadocs.dev/docs/mdx/collections
12
+
13
+// Extended schema with keywords for search
14
+const docsSchema = frontmatterSchema.extend({
15
+ keywords: z.array(z.string()).optional(),
16
+});
17
+
18
export const docs = defineDocs({
19
dir: 'content/docs',
20
docs: {
15
- schema: frontmatterSchema,
21
+ schema: docsSchema,
22
postprocess: {
23
includeProcessedMarkdown: true,
24
},
@@ -25,7 +31,7 @@ export const docs = defineDocs({
31
export const toolRouter = defineDocs({
32
dir: 'content/tool-router',
33
docs: {
28
- schema: frontmatterSchema,
34
+ schema: docsSchema,
35
},
36
meta: {
37
schema: metaSchema,
@@ -35,7 +41,7 @@ export const toolRouter = defineDocs({
41
export const reference = defineDocs({
42
dir: 'content/reference',
43
docs: {
38
- schema: frontmatterSchema,
44
+ schema: docsSchema,
45
},
46
meta: {
47
schema: metaSchema,
@@ -45,7 +51,7 @@ export const reference = defineDocs({
51
export const examples = defineDocs({
52
dir: 'content/examples',
53
docs: {
48
- schema: frontmatterSchema,
54
+ schema: docsSchema,
55
},
56
meta: {
57
schema: metaSchema,
@@ -55,7 +61,7 @@ export const examples = defineDocs({
61
export const toolkits = defineDocs({
62
dir: 'content/toolkits',
63
docs: {
58
- schema: frontmatterSchema,
64
+ schema: docsSchema,
65
},
66
meta: {
67
schema: metaSchema,