@devries-cameron20 / composio-1 / commits / 4f7d43f3b
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

Add changelog with timeline UI and migrate entries from Fern

- Add changelog collection in source.config.ts with date schema - Create timeline page at /docs/changelog with date + content layout - Add changelog link to docs sidebar - Migrate 18 changelog entries from Fern (09-15-25 to 12-29-25) - Add Accordion, Accordions, Callout components to MDX - Add CHANGELOG_GUIDE.md for developers writing new entries 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Sushmithamallesh committed Dec 29, 2025 at 23:04 UTC 4f7d43f3b3a3af821bd7a9bd6b181abae8eb3282
24 files changed +1761 -2
fumadocs/CHANGELOG_GUIDE.md new
+75
@@ -0,0 +1,75 @@
1 +# Changelog Guide
2 +
3 +## File Naming
4 +
5 +```
6 +MM-DD-YY.mdx # e.g., 12-29-25.mdx
7 +MM-DD-YY-suffix.mdx # Multiple same day: 12-10-25-masking.mdx
8 +```
9 +
10 +## Template
11 +
12 +```mdx
13 +---
14 +title: "Your Title Here"
15 +date: "YYYY-MM-DD"
16 +---
17 +
18 +Brief intro paragraph.
19 +
20 +### SDK Versions (if applicable)
21 +
22 +| SDK | Version |
23 +|-----|---------|
24 +| Python | v0.10.2 |
25 +| TypeScript | v0.3.1 |
26 +
27 +### Breaking Changes (if applicable)
28 +
29 +<Callout type="warn">
30 +**Breaking Change**
31 +
32 +What breaks and why.
33 +</Callout>
34 +
35 +**Before:**
36 +\`\`\`python
37 +old_code()
38 +\`\`\`
39 +
40 +**After:**
41 +\`\`\`python
42 +new_code()
43 +\`\`\`
44 +
45 +### What's New / Improvements / Bug Fixes
46 +
47 +- Change 1
48 +- Change 2
49 +```
50 +
51 +## Rules
52 +
53 +1. **Frontmatter required** — `title` and `date` (YYYY-MM-DD format)
54 +2. **No `#` heading** — Title renders automatically from frontmatter
55 +3. **Use `###` for sections** — Content headings start at h3
56 +4. **No emojis** — No checkmarks, warning symbols, etc.
57 +
58 +## Change Types
59 +
60 +| Type | How to Format |
61 +|------|---------------|
62 +| Breaking Change | `<Callout type="warn">` + before/after code + migration guide |
63 +| New Feature | `### What's New` |
64 +| Improvement | `### Improvements` |
65 +| Bug Fix | `### Bug Fixes` |
66 +| Deprecation | `<Callout>` with timeline |
67 +
68 +## Breaking Changes Checklist
69 +
70 +For any breaking change, include:
71 +- [ ] Before/after code examples
72 +- [ ] Migration guide with step-by-step instructions
73 +- [ ] Codemod (if applicable) — automated script to transform old code to new
74 +
75 +**What's a codemod?** A script that automatically updates user code. Instead of "change X to Y manually", users run the codemod and it transforms their code. See [jscodeshift](https://github.com/facebook/jscodeshift) or [ts-morph](https://github.com/dsherret/ts-morph).
fumadocs/app/(home)/docs/changelog/page.tsx new
+59
@@ -0,0 +1,59 @@
1 +import { changelogEntries, formatDate } from '@/lib/source';
2 +import { getMDXComponents } from '@/mdx-components';
3 +import {
4 + DocsBody,
5 + DocsDescription,
6 + DocsPage,
7 + DocsTitle,
8 +} from 'fumadocs-ui/layouts/docs/page';
9 +
10 +const mdxComponents = getMDXComponents();
11 +
12 +export default function ChangelogPage() {
13 + const entries = [...changelogEntries].sort(
14 + (a, b) => new Date(b.date).getTime() - new Date(a.date).getTime()
15 + );
16 +
17 + return (
18 + <DocsPage toc={[]} footer={{ enabled: false }}>
19 + <DocsTitle>Changelog</DocsTitle>
20 + <DocsDescription>New updates and improvements to Composio.</DocsDescription>
21 + <DocsBody>
22 + <div className="relative">
23 + {/* Timeline line */}
24 + <div className="absolute left-0 top-2 bottom-0 w-px bg-border hidden md:block md:left-[7.5rem]" />
25 +
26 + <div className="space-y-12">
27 + {entries.map((entry) => {
28 + const Content = entry.body;
29 +
30 + return (
31 + <article key={`${entry.date}-${entry.title}`} className="relative">
32 + {/* Date column */}
33 + <div className="mb-3 md:absolute md:left-0 md:w-24 md:text-right md:pr-8">
34 + <time className="text-sm font-medium text-muted-foreground">
35 + {formatDate(entry.date)}
36 + </time>
37 + </div>
38 +
39 + {/* Timeline dot */}
40 + <div className="hidden md:block absolute left-[7.5rem] top-1.5 -translate-x-1/2">
41 + <div className="w-2.5 h-2.5 rounded-full bg-primary ring-4 ring-background" />
42 + </div>
43 +
44 + {/* Content */}
45 + <div className="md:pl-36">
46 + <h2 className="text-2xl font-semibold mb-4">{entry.title}</h2>
47 + <div className="prose prose-neutral dark:prose-invert max-w-none">
48 + <Content components={mdxComponents} />
49 + </div>
50 + </div>
51 + </article>
52 + );
53 + })}
54 + </div>
55 + </div>
56 + </DocsBody>
57 + </DocsPage>
58 + );
59 +}
fumadocs/app/(home)/docs/layout.tsx
+14 -1
@@ -1,10 +1,23 @@
1 import { source } from '@/lib/source';
2 import { DocsLayout } from 'fumadocs-ui/layouts/docs';
3
4 +// Add changelog to the page tree
5 +const pageTree = {
6 + name: source.pageTree.name,
7 + children: [
8 + ...source.pageTree.children,
9 + {
10 + type: 'page' as const,
11 + name: 'Changelog',
12 + url: '/docs/changelog',
13 + },
14 + ],
15 +};
16 +
17 export default function Layout({ children }: LayoutProps<'/docs'>) {
18 return (
19 <DocsLayout
7 - tree={source.pageTree}
20 + tree={pageTree}
21 nav={{ enabled: false }}
22 searchToggle={{ enabled: false }}
23 sidebar={{ collapsible: false, footer: null }}
fumadocs/content/changelog/09-15-25.mdx new
+89
@@ -0,0 +1,89 @@
1 +---
2 +title: "Introducing Composio Auth Links"
3 +date: "2025-09-15"
4 +---
5 +
6 +Composio Auth Links provide a **hosted authentication solution** that eliminates the need for developers to build custom authentication forms. Instead of manually rendering OAuth consent screens, API key input forms, or custom authentication fields, developers can simply redirect users to a Composio-hosted URL that handles the entire authentication process automatically.
7 +
8 +### Why Use Auth Links?
9 +
10 +- **Zero UI Development**: No need to build forms for OAuth, API keys, or custom fields like subdomains
11 +- **Universal Authentication**: Works seamlessly across all supported third-party services
12 +- **Reduced Complexity**: Replace complex OAuth flows with a simple redirect
13 +- **Better UX**: Professional, consistent authentication experience for end users
14 +- **Faster Integration**: Get authentication working in minutes, not hours
15 +
16 +---
17 +
18 +### Python SDK (v0.8.11)
19 +
20 +**Added**
21 +
22 +- **Composio Connect Link Support**: New `link()` method for creating external authentication links
23 + - Added `link()` method to `ConnectedAccounts` class for generating user authentication links
24 + - Support for callback URL redirection after authentication
25 + - Enhanced user experience with external link-based authentication flow
26 + - **No manual form rendering required** - Composio handles all authentication UI
27 +
28 +**Examples:**
29 +
30 +```python
31 +# Basic usage - create a connection request
32 +connection_request = composio.connected_accounts.link('user_123', 'auth_config_123')
33 +redirect_url = connection_request.redirect_url
34 +print(f"Visit: {redirect_url} to authenticate your account")
35 +
36 +# Wait for the connection to be established
37 +connected_account = connection_request.wait_for_connection()
38 +
39 +# With callback URL
40 +connection_request = composio.connected_accounts.link(
41 + 'user_123',
42 + 'auth_config_123',
43 + callback_url='<https://your-app.com/callback>'
44 +)
45 +
46 +```
47 +
48 +### TypeScript SDK (v0.1.51)
49 +
50 +**Added**
51 +
52 +- **Composio Connect Links**: Added support for composio connect links
53 + - New `link()` method in `ConnectedAccounts` class for generating authentication URLs
54 + - Support for callback URL redirection with `CreateConnectedAccountLinkOptions`
55 + - Comprehensive TypeScript types and validation for link creation options
56 + - **Eliminates need for custom authentication forms** - just redirect users to the link
57 +
58 +**Examples:**
59 +
60 +```tsx
61 +// Basic usage - create a connection request
62 +const connectionRequest = await composio.connectedAccounts.link('user_123', 'auth_config_123');
63 +const redirectUrl = connectionRequest.redirectUrl;
64 +console.log(`Visit: ${redirectUrl} to authenticate your account`);
65 +
66 +// Wait for the connection to be established
67 +const connectedAccount = await connectionRequest.waitForConnection();
68 +
69 +// With callback URL
70 +const connectionRequest = await composio.connectedAccounts.link('user_123', 'auth_config_123', {
71 + callbackUrl: '<https://your-app.com/callback>'
72 +});
73 +
74 +```
75 +
76 +### Key Benefits
77 +
78 +- **No Form Building**: Composio handles OAuth consent, API key collection, and custom field inputs
79 +- **Hosted Authentication Flow**: Professional UI that works across all supported services
80 +- **Callback URL Support**: Control where users return after successful authentication
81 +- **Connection Waiting**: Built-in polling to detect when authentication completes
82 +- **Cross-Platform Consistency**: Identical developer experience across Python and TypeScript
83 +
84 +### Customisation
85 +
86 +You can customise the app logo and name showed in the authentication page via the dashboard. Head over your project via `platform.composio.dev` and choose Settings → Auth Links to upload a new logo and change the name.
87 +
88 +### Migration Note
89 +This feature replaces manual authentication form development with a simple redirect-based approach, significantly reducing integration time and complexity while providing a better user experience. Auth links are drop in replacement for `composio.connectedAccounts.initate`, you can safely swap this to `composio.connectedAccounts.link`
\ No newline at end of file
fumadocs/content/changelog/09-16-25.mdx new
+126
@@ -0,0 +1,126 @@
1 +---
2 +title: "Toolkit Versioning in SDKs"
3 +date: "2025-09-16"
4 +---
5 +
6 +Composio Toolkit Versioning provides **granular control over tool versions** across all your integrations. Instead of always using the latest version of tools, developers can now specify exact toolkit versions, ensuring consistent behavior and controlled updates in production environments.
7 +
8 +### Why Use Toolkit Versioning?
9 +
10 +- **Version Stability**: Pin specific toolkit versions to avoid unexpected changes in production
11 +- **Controlled Updates**: Test new toolkit versions before deploying to production
12 +- **Environment Consistency**: Ensure the same toolkit versions across development, staging, and production
13 +- **Rollback Capability**: Easily revert to previous toolkit versions if issues arise
14 +- **Fine-grained Control**: Set different versions for different toolkits based on your needs
15 +
16 +---
17 +
18 +### Python SDK (v0.8.11)
19 +
20 +**Added**
21 +
22 +- **Toolkit Versioning Support**: New `toolkit_versions` parameter for controlling tool versions
23 + - Added `toolkit_versions` parameter to `Composio` class initialization
24 + - Support for global version setting (e.g., `'latest'`)
25 + - Support for per-toolkit version mapping (e.g., `{'github': '20250902_00', 'slack': '20250902_00'}`)
26 + - Environment variable support with `COMPOSIO_TOOLKIT_VERSION_<TOOLKIT_NAME>` pattern
27 + - New `toolkit_version.py` utility module for version resolution logic
28 +
29 +**Examples:**
30 +
31 +```python
32 +# Global version for all toolkits, only `latest` is supported
33 +composio = Composio(toolkit_versions='latest')
34 +
35 +# Per-toolkit version mapping
36 +composio = Composio(toolkit_versions={
37 + 'github': '20250902_00',
38 + 'slack': '20250902_00',
39 + 'gmail': '20250901_01'
40 +})
41 +
42 +# Using environment variables
43 +# Set COMPOSIO_TOOLKIT_VERSION_GITHUB=20250902_00
44 +composio = Composio() # Automatically picks up env vars
45 +
46 +# Get tools with specific versions
47 +tools = composio.tools.get('default', {'toolkits': ['github']})
48 +```
49 +
50 +### TypeScript SDK (v0.1.52)
51 +
52 +**Added**
53 +
54 +- **Toolkit Versioning Support**: Added `toolkitVersions` configuration option
55 + - New `toolkitVersions` parameter in `Composio` class constructor
56 + - Support for global version string or per-toolkit version mapping
57 + - Environment variable parsing with `getToolkitVersionsFromEnv()` utility
58 + - Enhanced `getRawComposioToolBySlug()` method for version-specific tool retrieval
59 + - Version-aware tool filtering and search capabilities
60 +
61 +**Examples:**
62 +
63 +```typescript
64 +// Global version for all toolkits
65 +const composio = new Composio({
66 + toolkitVersions: '20250902_00'
67 +});
68 +
69 +// Per-toolkit version mapping
70 +const composio = new Composio({
71 + toolkitVersions: {
72 + 'github': '20250902_00',
73 + 'slack': '20250902_00',
74 + 'gmail': '20250901_01'
75 + }
76 +});
77 +
78 +// Using environment variables
79 +// Set COMPOSIO_TOOLKIT_VERSION_GITHUB=20250902_00
80 +const composio = new Composio(); // Automatically picks up env vars
81 +
82 +// Get specific tool version
83 +const tool = await composio.tools.getRawComposioToolBySlug(
84 + 'GITHUB_GET_REPO',
85 +);
86 +
87 +// Get tools with version-aware filtering
88 +const tools = await composio.tools.get('default', {
89 + toolkits: ['github'],
90 + limit: 10
91 +});
92 +```
93 +
94 +### Key Benefits
95 +
96 +- **Environment Variables**: Set `COMPOSIO_TOOLKIT_VERSION_<TOOLKIT_NAME>=<VERSION>` for automatic version resolution
97 +- **Flexible Configuration**: Choose between global versions or per-toolkit version mapping
98 +- **Backward Compatibility**: Existing code works unchanged - versioning is opt-in
99 +- **Version Fallback**: Automatically falls back to 'latest' when no version is specified
100 +- **Cross-Platform Consistency**: Identical developer experience across Python and TypeScript
101 +
102 +### Version Format
103 +
104 +Toolkit versions follow the format: `YYYYMMDD_NN` (e.g., `20250902_00`) or use `'latest'` for the most recent version only supported at global scope and not individual toolkit level.
105 +
106 +### Environment Variables
107 +
108 +```bash
109 +# Set specific versions for different toolkits
110 +export COMPOSIO_TOOLKIT_VERSION_GITHUB=20250902_00
111 +export COMPOSIO_TOOLKIT_VERSION_SLACK=20250902_00
112 +export COMPOSIO_TOOLKIT_VERSION_GMAIL=20250901_01
113 +```
114 +
115 +### Migration Note
116 +
117 +This feature is fully backward compatible. Existing code will continue to work without changes, using the latest versions by default. To enable versioning, simply add the `toolkit_versions` parameter during SDK initialization.
118 +
119 +---
120 +
121 +### Additional Updates
122 +
123 +- **Package Updates**: Bumped all Python provider packages to v0.8.10
124 +- **Documentation**: Enhanced API documentation with versioning examples
125 +- **Testing**: Added comprehensive test coverage (400+ new test cases) for versioning functionality
126 +- **Examples**: New versioning examples demonstrating practical usage patterns
fumadocs/content/changelog/09-26-25.mdx new
+515
@@ -0,0 +1,515 @@
1 +---
2 +title: "MCP (Model Control Protocol) & Experimental ToolRouter"
3 +date: "2025-09-26"
4 +---
5 +
6 +
7 +Composio now introduces **comprehensive MCP (Model Control Protocol) support** and an **experimental ToolRouter** for creating isolated, scoped sessions with advanced toolkit management. These features enable seamless integration with modern AI frameworks and provide powerful session-based tool routing capabilities.
8 +
9 +### Why Use MCP & ToolRouter?
10 +
11 +- **Framework Integration**: Native MCP support for Vercel AI, Mastra, OpenAI Agents, and LangChain
12 +- **Session Isolation**: Create isolated sessions with specific toolkit configurations
13 +- **Advanced Authentication**: Flexible auth config management per toolkit
14 +- **Scoped Access**: Control which tools are available within each session
15 +- **Multi-Service Workflows**: Route tool calls efficiently across different services
16 +- **Development & Testing**: Perfect for testing and development with scoped MCP server access
17 +
18 +### TypeScript SDK (v0.1.53)
19 +
20 +#### **Added: MCP API**
21 +
22 +**Core MCP Features:**
23 +- **MCP Server Creation**: Create and manage MCP server configurations
24 +- **User-Specific URLs**: Generate unique MCP server URLs for individual users
25 +- **Toolkit Configuration**: Support for multiple toolkits with custom auth configs
26 +- **Tool Filtering**: Specify allowed tools per configuration
27 +- **Connection Management**: Choose between manual and automatic account management
28 +
29 +**Basic Usage:**
30 +
31 +```typescript
32 +import { Composio } from '@composio/core';
33 +
34 +const composio = new Composio({
35 + apiKey: process.env.COMPOSIO_API_KEY,
36 +});
37 +
38 +// Create MCP configuration
39 +const mcpConfig = await composio.mcp.create('my-server-name', {
40 + toolkits: [
41 + { toolkit: 'github', authConfigId: 'ac_233434343' },
42 + { toolkit: 'gmail', authConfigId: 'ac_567890123' }
43 + ],
44 + allowedTools: ['GITHUB_CREATE_ISSUE', 'GMAIL_SEND_EMAIL'],
45 + manuallyManageConnections: false,
46 +});
47 +
48 +// Generate server instance for a user
49 +const serverInstance = await composio.mcp.generate('user123', mcpConfig.id);
50 +console.log('MCP URL:', serverInstance.url);
51 +```
52 +
53 +**Framework Integration Examples:**
54 +
55 +```typescript
56 +// Vercel AI Integration
57 +import { SSEClientTransport } from '@modelcontextprotocol/sdk/client/sse.js';
58 +import { experimental_createMCPClient as createMCPClient } from 'ai';
59 +
60 +const mcpClient = await createMCPClient({
61 + name: 'composio-mcp-client',
62 + transport: new SSEClientTransport(new URL(serverInstance.url)),
63 +});
64 +
65 +// Mastra Integration
66 +import { MCPClient as MastraMCPClient } from '@mastra/mcp';
67 +
68 +const mcpClient = new MastraMCPClient({
69 + servers: {
70 + composio: { url: new URL(mcpSession.url) },
71 + },
72 +});
73 +
74 +// OpenAI Agents Integration
75 +import { hostedMcpTool } from '@openai/agents';
76 +
77 +const tools = [
78 + hostedMcpTool({
79 + serverLabel: 'composio',
80 + serverUrl: mcpSession.url,
81 + }),
82 +];
83 +```
84 +
85 +#### **Added: Experimental ToolRouter**
86 +
87 +**Core ToolRouter Features:**
88 +- **Session-Based Routing**: Create isolated sessions for specific users and toolkit combinations
89 +- **Dynamic Configuration**: Configure toolkits and auth configs per session
90 +- **MCP Server URLs**: Each session gets a unique MCP server endpoint
91 +- **Flexible Toolkit Management**: Support for string names or detailed toolkit configurations
92 +- **Connection Control**: Manual or automatic connection management per session
93 +
94 +**Basic Usage:**
95 +
96 +```typescript
97 +// Create session with simple toolkit names
98 +const session = await composio.experimental.toolRouter.createSession('user_123', {
99 + toolkits: ['gmail', 'slack', 'github'],
100 +});
101 +
102 +// Create session with auth configs
103 +const session = await composio.experimental.toolRouter.createSession('user_456', {
104 + toolkits: [
105 + { toolkit: 'gmail', authConfigId: 'ac_gmail_work' },
106 + { toolkit: 'slack', authConfigId: 'ac_slack_team' },
107 + { toolkit: 'github', authConfigId: 'ac_github_personal' },
108 + ],
109 + manuallyManageConnections: true,
110 +});
111 +
112 +console.log('Session ID:', session.sessionId);
113 +console.log('MCP URL:', session.url);
114 +```
115 +
116 +**Advanced Multi-Service Integration:**
117 +
118 +```typescript
119 +// Complex workflow session
120 +const integrationSession = await composio.experimental.toolRouter.createSession('user_789', {
121 + toolkits: [
122 + { toolkit: 'gmail', authConfigId: 'ac_gmail_work' },
123 + { toolkit: 'slack', authConfigId: 'ac_slack_team' },
124 + { toolkit: 'github', authConfigId: 'ac_github_personal' },
125 + { toolkit: 'notion', authConfigId: 'ac_notion_workspace' },
126 + { toolkit: 'calendar', authConfigId: 'ac_gcal_primary' },
127 + ],
128 +});
129 +
130 +// Use with any MCP client
131 +const mcpClient = new MCPClient(integrationSession.url);
132 +```
133 +
134 +**Framework-Specific Examples:**
135 +
136 +```typescript
137 +// Mastra Integration
138 +const mcpSession = await composio.experimental.toolRouter.createSession(userId, {
139 + toolkits: ["gmail"],
140 + manuallyManageConnections: true,
141 +});
142 +
143 +const agent = new MastraAgent({
144 + name: 'Gmail Assistant',
145 + model: openai('gpt-4o-mini'),
146 + tools: await mcpClient.getTools(),
147 +});
148 +
149 +// OpenAI Agents Integration
150 +const tools = [
151 + hostedMcpTool({
152 + serverLabel: 'composio tool router',
153 + serverUrl: mcpSession.url,
154 + requireApproval: {
155 + never: { toolNames: ['GMAIL_FETCH_EMAILS'] },
156 + },
157 + }),
158 +];
159 +```
160 +
161 +
162 +
163 +### Python SDK (v0.8.17)
164 +
165 +#### **Added: MCP Support**
166 +
167 +**Core MCP Features:**
168 +- **Server Configuration**: Create and manage MCP server configurations
169 +- **Toolkit Management**: Support for both simple toolkit names and detailed configurations
170 +- **Authentication Control**: Per-toolkit auth config specification
171 +- **Tool Filtering**: Specify allowed tools across all toolkits
172 +- **User Instance Generation**: Generate user-specific MCP server instances
173 +
174 +**Basic Usage:**
175 +
176 +```python
177 +from composio import Composio
178 +
179 +composio = Composio()
180 +
181 +# Create MCP server with toolkit configurations
182 +server = composio.mcp.create(
183 + 'personal-mcp-server',
184 + toolkits=[
185 + {
186 + 'toolkit': 'github',
187 + 'auth_config_id': 'ac_xyz',
188 + },
189 + {
190 + 'toolkit': 'slack',
191 + 'auth_config_id': 'ac_abc',
192 + },
193 + ],
194 + allowed_tools=['GITHUB_CREATE_ISSUE', 'SLACK_SEND_MESSAGE'],
195 + manually_manage_connections=False
196 +)
197 +
198 +# Generate server instance for a user
199 +mcp_instance = server.generate('user_12345')
200 +print(f"MCP URL: {mcp_instance['url']}")
201 +```
202 +
203 +**Simple Toolkit Usage:**
204 +
205 +```python
206 +# Using simple toolkit names
207 +server = composio.mcp.create(
208 + 'simple-mcp-server',
209 + toolkits=['composio_search', 'text_to_pdf'],
210 + allowed_tools=['COMPOSIO_SEARCH_DUCK_DUCK_GO_SEARCH', 'TEXT_TO_PDF_CONVERT_TEXT_TO_PDF']
211 +)
212 +
213 +# All tools from toolkits (default behavior)
214 +server = composio.mcp.create(
215 + 'all-tools-server',
216 + toolkits=['composio_search', 'text_to_pdf']
217 + # allowed_tools=None means all tools from these toolkits
218 +)
219 +```
220 +
221 +**LangChain Integration:**
222 +
223 +```python
224 +import asyncio
225 +from composio import Composio
226 +from langchain_mcp_adapters.client import MultiServerMCPClient
227 +from langgraph.prebuilt import create_react_agent
228 +
229 +composio = Composio()
230 +
231 +mcp_config = composio.mcp.create(
232 + name="langchain-slack-mcp",
233 + toolkits=[{"toolkit": "slack", "auth_config_id": "<auth-config-id>"}],
234 +)
235 +
236 +mcp_server = mcp_config.generate(user_id='<user-id>')
237 +
238 +client = MultiServerMCPClient({
239 + "composio": {
240 + "url": mcp_server["url"],
241 + "transport": "streamable_http",
242 + }
243 +})
244 +
245 +async def langchain_mcp(message: str):
246 + tools = await client.get_tools()
247 + agent = create_react_agent("openai:gpt-4.1", tools)
248 + response = await agent.ainvoke({"messages": message})
249 + return response
250 +
251 +response = asyncio.run(langchain_mcp("Show me 20 most used slack channels"))
252 +```
253 +
254 +#### **Added: Experimental ToolRouter**
255 +
256 +**Core ToolRouter Features:**
257 +- **Session Management**: Create isolated tool routing sessions for users
258 +- **Toolkit Configuration**: Support for both simple toolkit names and detailed configurations
259 +- **Session Isolation**: Each session gets its own MCP URL and session ID
260 +- **Flexible Authentication**: Per-session auth config management
261 +- **Scoped Tool Access**: Control which tools are available within each session
262 +
263 +**Basic Usage:**
264 +
265 +```python
266 +from composio import Composio
267 +
268 +composio = Composio()
269 +
270 +# Create a tool router session
271 +session = composio.experimental.tool_router.create_session(
272 + user_id='user_123',
273 + toolkits=['github', 'slack'],
274 + manually_manage_connections=False
275 +)
276 +
277 +print(f"Session ID: {session['session_id']}")
278 +print(f"MCP URL: {session['url']}")
279 +```
280 +
281 +**Advanced Configuration:**
282 +
283 +```python
284 +# Create session with detailed toolkit configurations
285 +session = composio.experimental.tool_router.create_session(
286 + user_id='user_456',
287 + toolkits=[
288 + {
289 + 'toolkit': 'github',
290 + 'auth_config_id': 'ac_github_123'
291 + },
292 + {
293 + 'toolkit': 'slack',
294 + 'auth_config_id': 'ac_slack_456'
295 + }
296 + ],
297 + manually_manage_connections=True
298 +)
299 +
300 +# Minimal session (no specific toolkits)
301 +session = composio.experimental.tool_router.create_session(
302 + user_id='user_789'
303 +)
304 +```
305 +
306 +**Integration with AI Frameworks:**
307 +
308 +```python
309 +import asyncio
310 +from composio import Composio
311 +from langchain_mcp_adapters.client import MultiServerMCPClient
312 +
313 +composio = Composio()
314 +
315 +# Create tool router session
316 +session = composio.experimental.tool_router.create_session(
317 + user_id='ai_user',
318 + toolkits=['composio_search', 'text_to_pdf']
319 +)
320 +
321 +# Use with LangChain MCP client
322 +client = MultiServerMCPClient({
323 + "composio": {
324 + "url": session["url"],
325 + "transport": "streamable_http",
326 + }
327 +})
328 +
329 +async def use_tool_router():
330 + tools = await client.get_tools()
331 + # Use tools in your AI workflow
332 + return tools
333 +
334 +tools = asyncio.run(use_tool_router())
335 +```
336 +
337 +
338 +
339 +### Migration Guide
340 +
341 +#### **TypeScript SDK: Migrating to New MCP API**
342 +
343 +The new MCP API provides enhanced functionality and better integration patterns. Here's how to migrate from the previous MCP implementation:
344 +
345 +##### **Before (Legacy MCP)**
346 +
347 +```typescript
348 +// Legacy MCP approach (still accessible via deprecated.mcp)
349 +import { Composio } from '@composio/core';
350 +
351 +const composio = new Composio();
352 +
353 +// Old MCP server creation
354 +const legacyMCP = await composio.deprecated.mcp.createServer({
355 + name: 'my-server',
356 + toolkits: ['github', 'gmail'],
357 +});
358 +
359 +// Direct URL usage
360 +const mcpUrl = legacyMCP.url;
361 +```
362 +
363 +##### **After (New MCP API)**
364 +
365 +```typescript
366 +// New MCP API approach
367 +import { Composio } from '@composio/core';
368 +
369 +const composio = new Composio({
370 + apiKey: process.env.COMPOSIO_API_KEY,
371 +});
372 +
373 +// Step 1: Create MCP configuration
374 +const mcpConfig = await composio.mcp.create('my-server', {
375 + toolkits: [
376 + { toolkit: 'github', authConfigId: 'ac_github_123' },
377 + { toolkit: 'gmail', authConfigId: 'ac_gmail_456' }
378 + ],
379 + allowedTools: ['GITHUB_CREATE_ISSUE', 'GMAIL_SEND_EMAIL'],
380 + manuallyManageConnections: false,
381 +});
382 +
383 +// Step 2: Generate user-specific server instance
384 +const serverInstance = await composio.mcp.generate('user_123', mcpConfig.id);
385 +const mcpUrl = serverInstance.url;
386 +```
387 +
388 +##### **Key Migration Changes**
389 +
390 +1. **Two-Step Process**:
391 + - **Before**: Single step server creation
392 + - **After**: Create configuration, then generate user instances
393 +
394 +2. **Enhanced Configuration**:
395 + - **Before**: Simple toolkit names only
396 + - **After**: Detailed toolkit configs with auth, tool filtering, connection management
397 +
398 +3. **User-Specific URLs**:
399 + - **Before**: Single server URL for all users
400 + - **After**: Unique URLs per user for better isolation
401 +
402 +4. **Backward Compatibility**:
403 + - **Legacy Access**: Old MCP functionality remains available via `composio.deprecated.mcp`
404 + - **Gradual Migration**: Migrate at your own pace without breaking existing implementations
405 +
406 +##### **Migration Benefits**
407 +
408 +- **Better Security**: User-specific sessions with isolated access
409 +- **Enhanced Control**: Fine-grained toolkit and tool management
410 +- **Framework Integration**: Native support for modern AI frameworks
411 +- **Scalability**: Better resource management and user isolation
412 +
413 +##### **Migration Timeline**
414 +
415 +- **Phase 1**: New MCP API available alongside legacy implementation
416 +- **Phase 2**: Legacy MCP accessible via `deprecated.mcp` namespace
417 +- **Phase 3**: Full deprecation (timeline to be announced)
418 +
419 +**Recommendation**: Start new projects with the new MCP API and gradually migrate existing implementations to benefit from enhanced features and better framework integration.
420 +
421 +
422 +### Key Benefits & Use Cases
423 +
424 +#### **Development & Testing**
425 +- **Isolated Environments**: Test different toolkit combinations without affecting production
426 +- **Scoped Access**: Limit tool access for security and testing purposes
427 +- **Framework Flexibility**: Works with any MCP-compatible client or framework
428 +
429 +#### **Production Workflows**
430 +- **Multi-Service Integration**: Seamlessly combine tools from different services
431 +- **User-Specific Sessions**: Each user gets their own isolated session with appropriate permissions
432 +- **Authentication Management**: Fine-grained control over authentication per toolkit
433 +
434 +#### **Framework Compatibility**
435 +- **Vercel AI**: Native integration with Vercel AI SDK
436 +- **Mastra**: Full support for Mastra agents and workflows
437 +- **OpenAI Agents**: Direct integration with OpenAI's agent framework
438 +- **LangChain**: Complete LangGraph and LangChain compatibility
439 +- **Custom Clients**: Works with any MCP-compatible client
440 +
441 +#### **Enterprise Features**
442 +- **Session Management**: Track and manage multiple user sessions
443 +- **Resource Control**: Limit concurrent sessions and resource usage
444 +- **Audit Trail**: Full logging and monitoring of tool usage
445 +- **Security**: Isolated sessions prevent cross-user data access
446 +
447 +
448 +### Migration & Compatibility
449 +
450 +Both MCP and ToolRouter features are designed to complement existing Composio functionality:
451 +
452 +```typescript
453 +// Can be used alongside regular tool management
454 +const regularTools = await composio.tools.get({ toolkits: ['github'] });
455 +const mcpSession = await composio.experimental.toolRouter.createSession(userId, {
456 + toolkits: ['gmail', 'slack']
457 +});
458 +
459 +// Both approaches can coexist and serve different purposes
460 +```
461 +
462 +The experimental ToolRouter API provides a preview of advanced session management capabilities, while the MCP API offers production-ready Model Control Protocol support for modern AI frameworks.
463 +
464 +
465 +
466 +### Bug Fixes
467 +
468 +#### **Fixed: ToolRouter Dependency Issue**
469 +
470 +**Python SDK (v0.8.19)**
471 +
472 +**Issue Fixed:**
473 +- **ToolRouter Functionality**: Fixed ToolRouter tests that were failing due to missing `tool_router` attribute in HttpClient
474 +- **Dependency Update**: Updated `composio-client` dependency from version 1.9.1 to 1.10.0+ to include ToolRouter functionality
475 +- **Version Compatibility**: Resolved compatibility issues between ToolRouter implementation and client library
476 +
477 +**Details:**
478 +ToolRouter functionality was briefly broken in versions 0.8.15 to 0.8.18 due to a dependency version mismatch. The `composio-client` library version 1.9.1 did not include the `tool_router` attribute, causing all ToolRouter integration tests to fail with `AttributeError: 'HttpClient' object has no attribute 'tool_router'`.
479 +
480 +This has been fixed in version 0.8.19 by:
481 +- Updating the `composio-client` dependency to version 1.10.0+
482 +- Ensuring all ToolRouter functionality is now available
483 +- All ToolRouter integration tests now pass successfully
484 +
485 +**Previous Issue:**
486 +```python
487 +# This would fail in versions 0.8.15-0.8.18
488 +session = composio.experimental.tool_router.create_session(user_id='test')
489 +# AttributeError: 'HttpClient' object has no attribute 'tool_router'
490 +```
491 +
492 +**Fixed in 0.8.19:**
493 +```python
494 +# This now works correctly
495 +session = composio.experimental.tool_router.create_session(user_id='test')
496 +# Returns: {'session_id': '...', 'url': '...'}
497 +```
498 +
499 +#### **Fixed: Missing Descriptions in Auth Config Fields**
500 +
501 +**Python SDK (v0.8.17) & TypeScript SDK (v0.1.53)**
502 +
503 +**Issue Fixed:**
504 +- **Auth Config Connection Fields**: Added missing descriptions to toolkit auth configuration connection fields
505 +- **Auth Config Creation Fields**: Added missing descriptions to toolkit auth configuration creation fields
506 +- **Field Documentation**: Improved field documentation and help text for better developer experience
507 +
508 +**Details:**
509 +Previously, when developers were setting up auth configurations for toolkits, many fields lacked proper descriptions, making it difficult to understand what information was required. This fix ensures all auth config fields now include:
510 +
511 +- Clear, descriptive field labels
512 +- Helpful placeholder text where appropriate
513 +- Detailed explanations of field requirements
514 +
515 +This improvement affects all toolkits and makes the authentication setup process more intuitive and error-free.
fumadocs/content/changelog/10-22-25.mdx new
+52
@@ -0,0 +1,52 @@
1 +---
2 +title: "Adds Version Checks for Tool Execution and Improved Execution Speed in TS SDK"
3 +date: "2025-10-22"
4 +---
5 +
6 +
7 +### Summary
8 +Added version validation for manual tool execution to prevent unexpected behavior when using `latest` toolkit versions. This ensures users explicitly specify toolkit versions when executing tools manually, while allowing flexibility through a skip flag.
9 +
10 +This release also eliminates a lot of redundant API calls made to check connected account during tool execution, effectively increasing the performance of tool execution.
11 +
12 +### Key Changes
13 +
14 +#### Python SDK (`python/`)
15 +- Added `ToolVersionRequiredError` exception with detailed error messages and fix suggestions
16 +- Added `dangerously_skip_version_check` parameter to `execute()` method
17 +- Modified `_execute_tool()` to validate version is not `latest` unless skip flag is set
18 +- Automatically passes `dangerously_skip_version_check=True` for agentic provider flows
19 +- Added comprehensive test coverage (19 test methods) in `test_tool_execution.py`
20 +
21 +#### TypeScript SDK (`ts/packages/core/`)
22 +- Added `ComposioToolVersionRequiredError` error class with possible fixes
23 +- Added `dangerouslySkipVersionCheck` parameter to execute flow
24 +- Modified tool execution to validate version before API calls
25 +- Updated execution type definitions in `tool.types.ts` and `modifiers.types.ts`
26 +- Updated test files with date-based version format (`20251201_xx`)
27 +- Improved tool execution by eliminating redundant API calls
28 +
29 +### Behavior
30 +**Before:** Tools could be executed with `latest` version, risking unexpected behavior on toolkit updates
31 +
32 +**After:** Manual execution requires specific version or explicit skip flag:
33 +```python
34 +# Raises ToolVersionRequiredError
35 +tools.execute("GITHUB_CREATE_ISSUE", {...})
36 +
37 +# Works - explicit version
38 +tools.execute("GITHUB_CREATE_ISSUE", {...}, version="20251201_01")
39 +
40 +# Works - configured toolkit versions
41 +tools = Tools(client, provider, toolkit_versions={"github": "20251201_01"})
42 +
43 +# Works - with skip flag (use cautiously)
44 +tools.execute("GITHUB_CREATE_ISSUE", {...}, dangerously_skip_version_check=True)
45 +```
46 +
47 +### Breaking Changes
48 +Manual tool execution without version specification now throws an error. Users must either:
49 +1. Pass explicit version parameter
50 +2. Configure toolkit versions in SDK initialization
51 +3. Set environment variable `COMPOSIO_TOOLKIT_VERSION_<TOOLKIT_SLUG>`
52 +4. Use `dangerously_skip_version_check=True` flag
fumadocs/content/changelog/11-05-25.mdx new
+60
@@ -0,0 +1,60 @@
1 +---
2 +title: "Enhanced MCP URL Security Requirements"
3 +date: "2025-11-05"
4 +---
5 +
6 +We're introducing improved security requirements for Model Context Protocol (MCP) URLs to ensure better isolation between user connections and prevent unauthorized access.
7 +
8 +### What's Changing?
9 +
10 +Starting today, **all new Composio projects** must include at least one of the following parameters in their MCP URLs:
11 +- `user_id` - Identifies the specific user
12 +- `connected_account_id` - Identifies the specific connected account
13 +
14 +### Why This Matters
15 +
16 +This change ensures that:
17 +- **User Isolation**: Each user's connections remain completely separate from others
18 +- **Enhanced Security**: Prevents potential cross-user data access scenarios
19 +- **Better Multi-Tenancy**: Enables safer multi-tenant application architectures
20 +- **Explicit Access Control**: Forces developers to explicitly specify which user or account context they're operating in
21 +
22 +### Impact on Existing Projects
23 +
24 +**For existing projects**: We understand the importance of backward compatibility. While we've sent email notifications to project owners about upgrading their MCP URLs, your existing integrations will continue to work until **January 15th, 2026**.
25 +
26 +**Important**: After January 15th, 2026, MCP URLs without `user_id` or `connected_account_id` query parameters will no longer be supported. Please ensure you update your MCP URLs before this date to avoid service disruption.
27 +
28 +**Note**: If your MCP URLs already include either `user_id` or `connected_account_id` query parameters, no action is required—you can safely ignore this notice.
29 +
30 +### Implementation Example
31 +
32 +**Before:**
33 +```
34 +https://platform.composio.dev/v3/mcp/{id}
35 +```
36 +
37 +**After (with user_id):**
38 +```
39 +https://platform.composio.dev/v3/mcp/{id}?user_id=user_123
40 +```
41 +
42 +**After (with connected_account_id):**
43 +```
44 +https://platform.composio.dev/v3/mcp/{id}?connected_account_id=ca_xyz
45 +```
46 +
47 +### Migration Guide
48 +
49 +If you're using an existing project and want to adopt this security enhancement:
50 +
51 +1. Review your current MCP URL configuration
52 +2. Add either `user_id` or `connected_account_id` parameter to your URLs
53 +3. Update your application code to pass the appropriate identifier
54 +4. Test the updated URLs in your development environment
55 +
56 +For more details on choosing the right user identifiers for your application, see our [User Management documentation](https://docs.composio.dev/docs/user-management).
57 +
58 +### Questions?
59 +
60 +If you have any questions about this security enhancement or need assistance with migration, please reach out to our support team or check our [MCP documentation](#).
fumadocs/content/changelog/11-10-25.mdx new
+127
@@ -0,0 +1,127 @@
1 +---
2 +title: "Toolkit Version Support for Triggers"
3 +date: "2025-11-10"
4 +---
5 +
6 +### Summary
7 +Added toolkit version support to trigger operations (`create` and `getType`) in both Python and TypeScript SDKs. This allows users to explicitly specify which toolkit version to use when creating trigger instances and retrieving trigger type information, ensuring consistent behavior across different toolkit versions.
8 +
9 +Trigger operations now respect the global `toolkitVersions` configuration set during Composio initialization, providing better control over which trigger versions are used in your applications.
10 +
11 +### Key Changes
12 +
13 +#### TypeScript SDK (`ts/packages/core/`)
14 +- Added `toolkit_versions` parameter to `triggers.create()` method
15 + - Passes the global toolkit versions configuration when creating trigger instances
16 + - Defaults to `'latest'` when no version is specified
17 +- Modified `triggers.getType()` to respect global toolkit versions
18 + - Now accepts toolkit version configuration to fetch trigger types for specific versions
19 + - Improved error messages to include version-related fixes
20 +- Updated trigger type documentation with comprehensive examples
21 +- Added behavior documentation explaining version usage patterns
22 +
23 +#### Python SDK (`python/composio/core/models/`)
24 +- Added `toolkit_versions` parameter to `triggers.create()` method
25 + - Uses global toolkit version configuration when creating trigger instances
26 + - Converts `None` to `omit` for API compatibility
27 +- Modified `triggers.get_type()` to respect toolkit versions
28 + - Implemented custom method replacing direct client binding
29 + - Passes toolkit version configuration to API calls
30 +- Added comprehensive docstrings explaining version behavior
31 +
32 +### Behavior
33 +
34 +**Creating Triggers with Toolkit Versions:**
35 +
36 +```typescript
37 +// TypeScript - Configure versions at initialization
38 +const composio = new Composio({
39 + apiKey: 'your-api-key',
40 + toolkitVersions: {
41 + gmail: '12082025_00',
42 + github: '10082025_01'
43 + }
44 +});
45 +
46 +// Create trigger - uses version '12082025_00' for Gmail
47 +const trigger = await composio.triggers.create('user@example.com', 'GMAIL_NEW_MESSAGE', {
48 + connectedAccountId: 'ca_abc123',
49 + triggerConfig: {
50 + labelIds: 'INBOX',
51 + userId: 'me',
52 + interval: 60,
53 + },
54 +});
55 +```
56 +
57 +```python
58 +# Python - Configure versions at initialization
59 +composio = Composio(
60 + api_key="your-api-key",
61 + toolkit_versions={"gmail": "12082025_00", "github": "10082025_01"}
62 +)
63 +
64 +# Create trigger - uses version '12082025_00' for Gmail
65 +trigger = composio.triggers.create(
66 + slug="GMAIL_NEW_MESSAGE",
67 + user_id="user@example.com",
68 + trigger_config={"labelIds": "INBOX", "userId": "me", "interval": 60}
69 +)
70 +```
71 +
72 +**Retrieving Trigger Types with Specific Versions:**
73 +
74 +```typescript
75 +// TypeScript
76 +const composio = new Composio({
77 + apiKey: 'your-api-key',
78 + toolkitVersions: { github: '10082025_01' }
79 +});
80 +
81 +// Get trigger type for specific version
82 +const triggerType = await composio.triggers.getType('GITHUB_COMMIT_EVENT');
83 +// Returns trigger type for version '10082025_01'
84 +```
85 +
86 +```python
87 +# Python
88 +composio = Composio(
89 + api_key="your-api-key",
90 + toolkit_versions={"github": "10082025_01"}
91 +)
92 +
93 +# Get trigger type for specific version
94 +trigger_type = composio.triggers.get_type("GITHUB_COMMIT_EVENT")
95 +# Returns trigger type for version '10082025_01'
96 +```
97 +
98 +### Benefits
99 +
100 +- **Version Control**: Explicitly specify which toolkit version to use for triggers
101 +- **Consistency**: Ensure trigger behavior remains consistent across toolkit updates
102 +- **Testing**: Test trigger integrations with specific versions before updating
103 +- **Debugging**: Easier to debug issues by pinning to specific toolkit versions
104 +- **Production Safety**: Avoid unexpected changes from automatic version updates
105 +
106 +### Migration Guide
107 +
108 +This is a **non-breaking change**. Existing code will continue to work with default behavior:
109 +
110 +**Before (still works):**
111 +```typescript
112 +// Uses 'latest' version by default
113 +const trigger = await composio.triggers.create('user', 'GITHUB_COMMIT_EVENT', {...});
114 +```
115 +
116 +**After (recommended for production):**
117 +```typescript
118 +// Explicitly configure versions for better control
119 +const composio = new Composio({
120 + apiKey: 'your-api-key',
121 + toolkitVersions: { github: '10082025_01' }
122 +});
123 +
124 +const trigger = await composio.triggers.create('user', 'GITHUB_COMMIT_EVENT', {...});
125 +```
126 +
127 +For more details on toolkit versioning, see the [Toolkit Versioning documentation](/docs/toolkit-versioning).
fumadocs/content/changelog/11-13-25.mdx new
+37
@@ -0,0 +1,37 @@
1 +---
2 +title: "Required API Key Authentication for MCP URLs"
3 +date: "2025-11-13"
4 +---
5 +
6 +We're strengthening the security of Model Context Protocol (MCP) URLs by making API key authentication mandatory for all requests.
7 +
8 +### What's Changing?
9 +
10 +Starting **December 15th, 2025**, **all new Composio projects** must include the `x-api-key` header when making requests to MCP URLs. This header authenticates your application and ensures secure communication with the Composio platform.
11 +
12 +### Why This Matters
13 +
14 +This change provides:
15 +- **Enhanced Authentication**: Ensures only authorized applications can access MCP endpoints
16 +- **Industry Best Practices**: Aligns with standard API security patterns
17 +
18 +### Impact on Existing Projects
19 +
20 +**For existing projects**: We value backward compatibility and understand the need for a smooth transition. Your existing MCP URLs will continue to work without the `x-api-key` header until **April 15th, 2026**.
21 +
22 +**Important**: After April 15th, 2026, all MCP URL requests without the `x-api-key` header will be rejected. Please ensure you update your applications before this date to avoid service disruption.
23 +
24 +**Note**: If you're already passing the `x-api-key` header in your MCP requests, no action is required—you're all set!
25 +
26 +### Migration Guide
27 +
28 +To adopt this security enhancement in your existing projects:
29 +
30 +1. **Locate Your API Key**: Find your API key in the Composio dashboard under Project Settings
31 +2. **Update Your Code**: Add the `x-api-key` header to all MCP URL requests
32 +3. **Test Thoroughly**: Verify the updated requests work in your development environment
33 +4. **Deploy**: Roll out the changes to your production environment
34 +
35 +### Questions?
36 +
37 +If you have any questions about this security enhancement or need assistance with migration, please reach out to our support team or check our [MCP documentation](https://docs.composio.dev/docs/mcp).
fumadocs/content/changelog/12-03-25.mdx new
+25
@@ -0,0 +1,25 @@
1 +---
2 +title: "Connected Account Expiration for Incomplete Connections"
3 +date: "2025-12-03"
4 +---
5 +
6 +We're implementing automatic expiration for connected accounts that remain in incomplete states, helping maintain a cleaner and more efficient authentication system.
7 +
8 +### What's Changing?
9 +
10 +Connected accounts in `Initializing` and `Initiated` states will now automatically expire after **10 minutes**. This applies to connection attempts that were started but never completed.
11 +
12 +### Why This Matters
13 +
14 +This change provides:
15 +- **Better Resource Management**: Automatically cleans up incomplete connection attempts
16 +- **Improved System Hygiene**: Prevents accumulation of stale, unused connection records
17 +- **Enhanced User Experience**: Reduces clutter from abandoned authentication flows
18 +
19 +<Callout>
20 +This is a **non-breaking change**. Your existing integrations and completed connections will continue to work as expected. This change only affects connection attempts that are never completed.
21 +</Callout>
22 +
23 +### Questions?
24 +
25 +If you have any questions about this change, please reach out to our support team or check our [Connected Accounts documentation](https://docs.composio.dev/docs/connected-accounts).
fumadocs/content/changelog/12-09-25.mdx new
+38
@@ -0,0 +1,38 @@
1 +---
2 +title: "Transition to Self-Managed Credentials for Select Applications"
3 +date: "2025-12-09"
4 +---
5 +
6 +<Callout>
7 +This is a **non-breaking change**. Your existing integrations will continue to work as expected. This change only affects new integrations with the applications listed below.
8 +</Callout>
9 +
10 +### What's Changing?
11 +
12 +Starting today, the following applications will require **your own developer credentials** instead of Composio-managed credentials:
13 +
14 +- **Auth0**
15 +- **Blackbaud**
16 +- **BoldSign**
17 +- **Deel**
18 +- **Front**
19 +- **GoToWebinar**
20 +- **PagerDuty**
21 +- **Pipedrive**
22 +- **Shopify**
23 +- **Strava**
24 +- **SurveyMonkey**
25 +- **Webex**
26 +
27 +### What You Need to Do
28 +
29 +To continue using these applications with Composio:
30 +
31 +1. **Create Developer Accounts**: Register for developer accounts on the platforms you need
32 +2. **Generate API Credentials**: Create OAuth apps following each platform's documentation
33 +3. **Configure in Composio**: Add your credentials to Composio using [custom auth configs](https://docs.composio.dev/docs/custom-auth-configs)
34 +4. **Test Your Integration**: Test your integration with the new credentials
35 +
36 +<Callout>
37 +All other Composio applications continue to work with Composio-managed credentials. This change only affects the 12 applications listed above.
38 +</Callout>
fumadocs/content/changelog/12-10-25-labels-deprecation.mdx new
+18
@@ -0,0 +1,18 @@
1 +---
2 +title: "Removal of label query parameter from connected accounts API"
3 +date: "2025-12-10"
4 +---
5 +
6 +The `label` query parameter has been removed from the `GET /api/v3/connected_accounts` endpoint.
7 +
8 +### What's changing?
9 +
10 +The `label` query parameter is no longer supported when listing connected accounts. This parameter was previously accepted but had no functional behavior since label ingestion was removed in an earlier update.
11 +
12 +### Impact
13 +
14 +**None** - This is a cleanup change. The `label` query parameter was not performing any filtering since the underlying label ingestion functionality was already removed. If your code was passing this parameter, it was being silently ignored.
15 +
16 +### Migration
17 +
18 +No action required. If your code was passing the `label` query parameter, you can safely remove it from your API calls.
fumadocs/content/changelog/12-10-25-masking.mdx new
+25
@@ -0,0 +1,25 @@
1 +---
2 +title: "Enhanced Security Masking for Sensitive Fields"
3 +date: "2025-12-10"
4 +---
5 +
6 +We've improved the security masking for `REDACTED` fields in the following APIs:
7 +
8 +- [Get Connected Account](https://docs.composio.dev/rest-api/connected-accounts/get-connected-accounts-by-nanoid)
9 +- [List Connected Accounts](https://docs.composio.dev/rest-api/connected-accounts/get-connected-accounts)
10 +
11 +**What's Changed:**
12 +Sensitive fields are now partially masked, revealing only the **first 4 characters** to help with debugging while maintaining security.
13 +
14 +**Example:**
15 +```
16 +Before: REDACTED
17 +After: abcd...
18 +```
19 +
20 +### Disabling Masking
21 +
22 +If you need to disable masking for your use case, you have two options:
23 +
24 +1. **Via UI:** Navigate to **Project Settings** → **Configuration** tab and update the masking settings
25 +2. **Via API:** Use the [Patch Project Config API](https://docs.composio.dev/rest-api/projects/patch-org-project-config)
fumadocs/content/changelog/12-10-25.mdx new
+102
@@ -0,0 +1,102 @@
1 +---
2 +title: "Typed Responses Across Toolkits"
3 +date: "2025-12-10"
4 +---
5 +
6 +We've updated many toolkits so their outputs are now strongly typed objects instead of a generic `response_data` blob, meaning tools like Outlook, HubSpot, Notion, etc. now return well-shaped, documented fields you can rely on directly in your code and agents. These improvements apply to the latest toolkit versions—see our [toolkit versioning docs](https://docs.composio.dev/docs/toolkit-versioning) for how versions are managed.
7 +
8 +<Callout type="warn">
9 +**Breaking Change for `latest` Version**
10 +
11 +If you're using the `latest` version and your code post-processes the old `response_data` structure, you'll need to update your code to work with the new flattened, typed response schemas.
12 +</Callout>
13 +
14 +### Why This Matters
15 +- Better developer experience for direct execute: clear fields and types
16 +- Improved agent performance: flatter output shapes with explicit fields reduce nesting and invalid params
17 +- Clearer docs and type safety: richer metadata for IDEs and autocomplete
18 +
19 +<Accordions>
20 +<Accordion title="Impacted Toolkits (57 total)">
21 +
22 +#### Communication & Collaboration
23 +discordbot, microsoft_teams, slack, zoom
24 +
25 +#### CRM & Sales
26 +apollo, attio, hubspot, instantly, intercom, kommo, salesforce
27 +
28 +#### Productivity & Docs
29 +coda, confluence, googledocs, googletasks, notion, todoist
30 +
31 +#### Marketing & Social Media
32 +facebook, instagram, klaviyo, linkedin, metaads, reddit, tiktok
33 +
34 +#### E-commerce & Payments
35 +brex, quickbooks, ramp, shopify, square, stripe, xero
36 +
37 +#### Project Management
38 +clickup, linear
39 +
40 +#### Design & Creative
41 +canva, figma
42 +
43 +#### Data & Analytics
44 +ahrefs, airtable, apify, exa, pplx, serpapi, tavily
45 +
46 +#### Email & Calendar
47 +calendly, outlook
48 +
49 +#### Storage & Files
50 +one_drive
51 +
52 +#### Web Tools
53 +firecrawl, fireflies, google_maps, google_search_console
54 +
55 +#### AI & Media
56 +elevenlabs, heygen, lmnt, mem0
57 +
58 +#### Customer Support
59 +freshdesk, zendesk
60 +
61 +#### Video & Content
62 +youtube
63 +
64 +</Accordion>
65 +</Accordions>
66 +
67 +### Before vs After
68 +**Previous (generic, version `20251202_00`):**
69 +```json
70 +{
71 + "data": {
72 + "response_data": { "...": "..." }
73 + },
74 + "successful": true
75 +}
76 +```
77 +
78 +**Now (typed example – Outlook List Messages, version `20251209_00`):**
79 +```json
80 +{
81 + "data": {
82 + "@odata.context": "https://graph.microsoft.com/v1.0/$metadata#users('me')/messages",
83 + "@odata.nextLink": "https://graph.microsoft.com/v1.0/me/messages?$skip=10",
84 + "value": [
85 + {
86 + "id": "abc123",
87 + "subject": "Hi there",
88 + "from": { "emailAddress": { "address": "a@b.com", "name": "Alice" } },
89 + "hasAttachments": true
90 + }
91 + ]
92 + },
93 + "successful": true
94 +}
95 +```
96 +
97 +For the exact field mapping per toolkit, open `platform.composio.dev` → Toolkits → List Messages (or the relevant tool).
98 +
99 +### Migration Notes
100 +- Breaking change for consumers on the `latest` version who post-process the old nested `response_data` shape: outputs are now flattened and explicitly typed.
101 +- New and modified fields include richer descriptions and examples; some legacy placeholders were removed.
102 +- Re-fetch schemas for your tool/version to see the typed definitions. Use the toolkit view in `platform.composio.dev` for authoritative field details.
fumadocs/content/changelog/12-15-25.mdx new
+24
@@ -0,0 +1,24 @@
1 +---
2 +title: "Tool Router General Availability"
3 +date: "2025-12-15"
4 +---
5 +
6 +The Composio SDKs achieved a significant milestone with Tool Router moving from experimental to stable production status in December 2025. The Tool Router is now a fully supported feature that enables creating isolated MCP sessions with scoped toolkit access across both Python 0.10.1 and TypeScript 0.3.0.
7 +
8 +### Major Achievements
9 +
10 +**Native Tool Execution:** Both SDKs now support direct tool execution through Tool Router sessions. The TypeScript implementation emphasizes improved type safety and error handling, while Python developers benefit from better integration with provider-wrapped tools.
11 +
12 +**Webhook Security:** A new verification method was introduced. The system now provides secure webhook endpoint validation and signature verification for incoming webhooks, enhancing protection for trigger-based workflows.
13 +
14 +**Framework Compatibility:** The stable Tool Router integrates with multiple AI platforms including OpenAI, Anthropic, LangChain, LlamaIndex, CrewAI, and Vercel AI SDK.
15 +
16 +### Technical Improvements
17 +
18 +The TypeScript SDK resolved significant CommonJS compatibility issues by switching bundlers. This addresses a common developer pain point, particularly for Node.js projects not using ES modules.
19 +
20 +The Python SDK extended LangChain provider support to version 1, while simultaneously fixing a critical KeyError occurring when SUPABASE_BETA_RUN_SQL_QUERY is used with Agents.
21 +
22 +### Migration Path
23 +
24 +Users upgrading from experimental APIs should note the simplified approach—the Tool Router API now operates directly rather than through experimental namespaces, with comprehensive migration documentation provided.
fumadocs/content/changelog/12-16-25.mdx new
+62
@@ -0,0 +1,62 @@
1 +---
2 +title: "Deprecation of is_local_toolkit Field and Removal of is_local Query Parameter"
3 +date: "2025-12-16"
4 +---
5 +
6 +We're cleaning up the Toolkits API by deprecating the `is_local_toolkit` response field and removing the `is_local` query parameter filter.
7 +
8 +### What's Changing?
9 +
10 +#### Response Field: `is_local_toolkit` (Deprecated)
11 +
12 +The `is_local_toolkit` field in toolkit API responses is now **deprecated**. This field was originally intended to indicate whether a toolkit was local to a specific project, but it is no longer meaningful as no toolkits use this classification.
13 +
14 +**Affected Endpoints:**
15 +- `GET /api/v3/toolkits` - List toolkits
16 +- `GET /api/v3/toolkits/{slug}` - Get single toolkit
17 +- `GET /api/v3/toolkits/multi` - Get multiple toolkits
18 +
19 +The field will continue to be returned in API responses for backward compatibility, but it will always return `false`. It is marked as `deprecated: true` in the OpenAPI specification.
20 +
21 +#### Query Parameter: `is_local` (Removed)
22 +
23 +The `is_local` query parameter filter has been **removed** from the following endpoints:
24 +- `GET /api/v3/toolkits`
25 +- `GET /api/v3/toolkits/multi`
26 +
27 +This parameter was used to filter toolkits by their local status, but since no toolkits are classified as local, it served no practical purpose.
28 +
29 +### Impact on Your Code
30 +
31 +#### If You're Using the `is_local` Query Parameter
32 +
33 +**Before:**
34 +```typescript
35 +// This will no longer work
36 +const toolkits = await fetch('/api/v3/toolkits?is_local=true');
37 +```
38 +
39 +**After:**
40 +```typescript
41 +// Simply remove the is_local parameter
42 +const toolkits = await fetch('/api/v3/toolkits');
43 +```
44 +
45 +#### If You're Reading the `is_local_toolkit` Response Field
46 +
47 +The field will continue to be present in responses but will always return `false`. You can safely ignore this field or remove any logic that depends on it.
48 +
49 +**Before:**
50 +```typescript
51 +const toolkit = await composio.toolkits.get('github');
52 +if (toolkit.is_local_toolkit) {
53 + // This condition will never be true
54 + handleLocalToolkit(toolkit);
55 +}
56 +```
57 +
58 +**After:**
59 +```typescript
60 +const toolkit = await composio.toolkits.get('github');
61 +// Remove is_local_toolkit checks - they're no longer meaningful
62 +```
fumadocs/content/changelog/12-19-25.mdx new
+57
@@ -0,0 +1,57 @@
1 +---
2 +title: "Toolkit Deprecation: Streamlining Our Platform"
3 +date: "2025-12-19"
4 +---
5 +
6 +### What's Changed
7 +
8 +We're deprecating **60 toolkits** that currently have no supported actions. These toolkits will be reactivated once we add functional actions to them, ensuring you only see integrations that are ready to use.
9 +
10 +### Deprecated Toolkits
11 +
12 +The following toolkits are now deprecated:
13 +
14 +- `ACCELO`, `ADOBE`, `AERO_WORKFLOW`, `AMAZON`, `APEX27`
15 +- `APPOINTO`, `APPSFLYER`, `ATLASSIAN`, `AUTH0`, `AXONAUT`
16 +- `BATTLENET`, `BOLDSIGN`, `BRAINTREE`, `BREEZY_HR`, `BREX_STAGING`
17 +- `BRIGHTPEARL`, `BROWSERHUB`, `CUSTOMER_IO`, `DEEL`, `DRIP_JOBS`
18 +- `EPIC_GAMES`, `FACTORIAL`, `FITBIT`, `FRONT`, `GO_TO_WEBINAR`
19 +- `GURU`, `HELCIM`, `HIGHLEVEL`, `ICIMS_TALENT_CLOUD`, `IDEA_SCALE`
20 +- `KEAP`, `LASTPASS`, `LEVER_SANDBOX`, `LEXOFFICE`, `MANY_CHAT`
21 +- `MBOUM`, `MICROSOFT_TENANT`, `MOXIE`, `ONCEHUB`, `POPTIN`
22 +- `PRECORO`, `PRINTNODE`, `QUALAROO`, `RAVENSEOTOOLS`, `RING_CENTRAL`
23 +- `RIPPLING`, `SAGE`, `SALESFORCE_MARKETING_CLOUD`, `SEISMIC`, `SMARTRECRUITERS`
24 +- `TAPFORM`, `TERMINUS`, `TIMEKIT`, `TWITCH`, `VENLY`
25 +- `VERO`, `VISME`, `WAVE_ACCOUNTING`, `WIZ`, `ZOHO_DESK`
26 +
27 +### Impact on Your Integration
28 +
29 +#### API Behavior Changes
30 +
31 +**List Toolkits Endpoint**
32 +
33 +The [GET /toolkits](https://docs.composio.dev/rest-api/toolkits/get-toolkits) endpoint will now exclude deprecated toolkits by default.
34 +
35 +**Need to see deprecated toolkits?** Use the new `include_deprecated` query parameter.
36 +
37 +#### Backward Compatibility
38 +
39 +**Your existing integrations are safe.** All other endpoints continue to work with deprecated toolkits:
40 +
41 +- Retrieve the toolkit details
42 +- Create auth configurations
43 +- Manage connected accounts
44 +- Configure MCP Servers
45 +
46 +This ensures zero breaking changes to your current implementations.
47 +
48 +### Why This Matters
49 +
50 +This change helps you:
51 +- **Focus on working integrations** - No clutter from non-functional toolkits
52 +- **Avoid integration attempts** with toolkits that have no actions
53 +- **Better developer experience** with a cleaner, more actionable toolkit list
54 +
55 +### Questions?
56 +
57 +If you have questions or need support with any deprecated toolkit, reach out to our team or check our [documentation](https://docs.composio.dev).
fumadocs/content/changelog/12-22-25.mdx new
+48
@@ -0,0 +1,48 @@
1 +---
2 +title: "Toolkit Deprecation: Removing Empty Toolkits"
3 +date: "2025-12-22"
4 +---
5 +
6 +### What's Changed
7 +
8 +We're deprecating **15 toolkits** that currently have no supported actions. These toolkits will be reactivated once we add functional actions to them, ensuring you only see integrations that are ready to use.
9 +
10 +### Deprecated Toolkits
11 +
12 +The following toolkits are now deprecated:
13 +
14 +- `BREATHEHR`, `DIXA`, `EGNYTE`, `EXPENSIFY`, `FREEAGENT`
15 +- `GUSTO`, `NUTSHELL`, `OPENNUTRITION`, `OYSTERHR`, `RAKUTEN`
16 +- `SALESFLARE`, `TEAMLEADER`, `WALGREENS`, `WHOOP`, `WIX`
17 +
18 +### Impact on Your Integration
19 +
20 +#### API Behavior Changes
21 +
22 +**List Toolkits Endpoint**
23 +
24 +The [GET /toolkits](https://docs.composio.dev/rest-api/toolkits/get-toolkits) endpoint will now exclude deprecated toolkits by default.
25 +
26 +**Need to see deprecated toolkits?** Use the `include_deprecated` query parameter.
27 +
28 +#### Backward Compatibility
29 +
30 +**Your existing integrations are safe.** All other endpoints continue to work with deprecated toolkits:
31 +
32 +- Retrieve the toolkit details
33 +- Create auth configurations
34 +- Manage connected accounts
35 +- Configure MCP Servers
36 +
37 +This ensures zero breaking changes to your current implementations.
38 +
39 +### Why This Matters
40 +
41 +This change helps you:
42 +- **Focus on working integrations** - No clutter from non-functional toolkits
43 +- **Avoid integration attempts** with toolkits that have no actions
44 +- **Better developer experience** with a cleaner, more actionable toolkit list
45 +
46 +### Questions?
47 +
48 +If you have questions or need support with any deprecated toolkit, reach out to our team or check our [documentation](https://docs.composio.dev).
fumadocs/content/changelog/12-26-25.mdx new
+92
@@ -0,0 +1,92 @@
1 +---
2 +title: "Authentication Updates Across Multiple Toolkits"
3 +date: "2025-12-26"
4 +---
5 +
6 +We've updated authentication configurations for several toolkits to improve security, fix issues, and support additional deployment options.
7 +
8 +### Summary
9 +
10 +| Toolkit | Change Type | Action Required |
11 +|-------------|-------------|-----------------|
12 +| Ashby | Deprecated | No |
13 +| Freshdesk | Deprecated | No |
14 +| Freshservice | Deprecated | No |
15 +| Make | Breaking | New auth config + user reconnect |
16 +| Mixpanel | Fix | No |
17 +| Recall AI | Breaking | New auth config + user reconnect |
18 +| Relevance AI | Breaking | New auth config + user reconnect |
19 +| SmartRecruiters | Breaking | New auth config + user reconnect |
20 +| Supabase | Improvement | No |
21 +| Trello | Deprecated | No |
22 +| ZoomInfo | Deprecated | No |
23 +
24 +### Breaking Changes
25 +
26 +These toolkits had incorrect or outdated authentication configurations that needed fixing. We verified that active usage for these toolkits is practically zero before proceeding with these changes.
27 +
28 +**Impact**: Existing connections will stop working. You'll need to create new auth configs and ask affected users to reconnect.
29 +
30 +#### Make
31 +
32 +Replaced region-based configuration with full base URL input. Users now provide the complete Make instance URL (e.g., `https://us2.make.com` or `https://us1.make.celonis.com`) instead of just a region code.
33 +
34 +#### Recall AI
35 +
36 +Updated from region-based to full base URL configuration. Fixed field descriptions and metadata. Updated categories to AI/Productivity/Communication and added proper documentation links.
37 +
38 +#### Relevance AI
39 +
40 +Simplified authentication by removing deprecated Project ID field. Added conditional mapping for region codes to API subdomains (AU→f1db6c, EU→d7b62b, US→bcbe5a). Region field now defaults to US.
41 +
42 +#### SmartRecruiters
43 +
44 +Fixed OAuth configuration with correct SmartRecruiters endpoints. Added proper default scopes for candidates, jobs, and users. Enabled PKCE and added refresh token support.
45 +
46 +### Deprecated (Still Working)
47 +
48 +These changes introduce new auth methods while keeping old ones functional:
49 +
50 +#### Ashby
51 +
52 +Added new API Key authentication scheme with automatic base64 encoding and proper authorization headers.
53 +
54 +**No Action Required**: Old Basic Auth method is deprecated but continues to work. Existing connections are unaffected.
55 +
56 +#### Freshdesk
57 +
58 +Added new API Key authentication scheme requiring subdomain and API key with automatic base64 encoding.
59 +
60 +**No Action Required**: Old Basic Auth method is deprecated but continues to work. Existing connections are unaffected.
61 +
62 +#### Freshservice
63 +
64 +Added new API Key authentication scheme requiring subdomain and API key with automatic base64 encoding.
65 +
66 +**No Action Required**: Old Basic Auth method is deprecated but continues to work. Existing connections are unaffected.
67 +
68 +#### Trello
69 +
70 +Marked Bearer Token authentication as deprecated in favor of OAuth authentication.
71 +
72 +**No Action Required**: Old Bearer auth continues to function. OAuth is recommended for new connections.
73 +
74 +#### ZoomInfo
75 +
76 +Added new OAuth2 authentication scheme with comprehensive scopes for contacts, companies, audiences, scoops, news, and intent data. Deprecated the old JWT-based Basic authentication. Password field now properly marked as secret.
77 +
78 +**No Action Required**: Old JWT auth continues to function. New connections will use OAuth2.
79 +
80 +### Non-Breaking Improvements
81 +
82 +#### Mixpanel
83 +
84 +Fixed region mapping logic for data residency. Added proper conditional evaluation to map regions to correct API hosts (EU, India, or Standard). Region field is now optional and defaults to Standard server. Service account secret now properly marked as secret.
85 +
86 +**No Action Required**: Existing connections continue to work without changes.
87 +
88 +#### Supabase
89 +
90 +Changed `base_url` field type from `auth_config_field` to `connection_field` for both OAuth and API Key schemes. Updated base action logic to respect user-provided base URLs, enabling support for self-hosted Supabase instances.
91 +
92 +**No Action Required**: Existing connections continue to work. Self-hosted instances now supported.
fumadocs/content/changelog/12-29-25.mdx new
+89
@@ -0,0 +1,89 @@
1 +---
2 +title: "Authentication & Configuration Updates Across Multiple Toolkits"
3 +date: "2025-12-29"
4 +---
5 +
6 +### Summary
7 +
8 +This release includes significant authentication and configuration improvements across 16+ toolkits. The changes standardize Base URL handling, modernize authentication methods, and fix various endpoint configurations to improve reliability and flexibility.
9 +
10 +| Toolkit | Change Type | Description |
11 +|---------|-------------|-------------|
12 +| **Make** | Breaking | Removed Region field, replaced with Base URL |
13 +| **Linear** | Improvement | Base URL is no longer configurable |
14 +| **Kibana** | Improvement | Removed default value for Base URL |
15 +| **Insightly** | Fix | Added default value for Pod field |
16 +| **HelloBar** | Deprecated | Deprecated bearer authentication |
17 +| **Gong** | Fix | Added default value for Base URL |
18 +| **FormSite** | Deprecated | Deprecated bearer auth, added API key authentication |
19 +| **DataScope** | Fix | Fixed Get Current User Endpoint |
20 +| **D2L Brightspace** | Fix | Updated Get Current User Endpoint |
21 +| **ClickUp** | Fix | Changed Base URL field type |
22 +| **Bubble** | Breaking | Fixed Base URL field, removed Subdomain |
23 +| **Brilliant Directories** | Fix | Implemented dynamic Base URL for user endpoint |
24 +| **Braintree** | Improvement | Updated to production defaults with dynamic endpoints |
25 +| **Auth0** | Improvement | Replaced hardcoded endpoint with dynamic tenant Base URL |
26 +
27 +### Breaking Changes
28 +
29 +We verified that active usage for these toolkits is practically zero before proceeding with these changes.
30 +
31 +#### Make Toolkit
32 +- **Removed Region field** in favor of explicit Base URL configuration
33 +- Users must now provide the full Base URL instead of selecting a region
34 +- This change provides more flexibility for custom deployments and regional endpoints
35 +
36 +#### Bubble Toolkit
37 +- **Removed Subdomain field** and restructured Base URL handling
38 +- Users must now provide the complete Base URL instead of just the Subdomain
39 +- This change standardizes URL configuration across all toolkits
40 +
41 +### Deprecated Features
42 +
43 +#### HelloBar Toolkit
44 +- **Bearer authentication is now deprecated**
45 +- While still functional, users are encouraged to migrate to newer authentication methods
46 +- Support for bearer tokens will be removed in a future release
47 +
48 +#### FormSite Toolkit
49 +- **Bearer authentication deprecated** in favor of API key authentication
50 +- New integrations should use API key authentication for improved security
51 +- Existing bearer token implementations will continue to work but should be migrated
52 +
53 +### Improvements & Fixes
54 +
55 +#### Configuration Improvements
56 +
57 +**Linear Toolkit** - Base URL is no longer a configurable field. The toolkit now uses a fixed endpoint, simplifying the authentication process.
58 +
59 +**Kibana Toolkit** - Removed the default value for Base URL, allowing for more flexible deployment configurations. Users can now specify custom Kibana instances without overriding defaults.
60 +
61 +**Gong Toolkit** - Added a sensible default value for Base URL to simplify initial setup. New users can connect without manually configuring the endpoint.
62 +
63 +**Insightly Toolkit** - Added default value for the Pod field to streamline configuration. Reduces setup complexity for standard deployments.
64 +
65 +**ClickUp Toolkit** - Fixed the Base URL field type for proper validation and handling. Ensures consistent URL formatting across all operations.
66 +
67 +#### Dynamic Endpoint Updates
68 +
69 +**Brilliant Directories Toolkit** - Implemented dynamic Base URL resolution for the Get Current User Endpoint. Automatically adapts to different deployment environments.
70 +
71 +**Braintree Toolkit** - Updated configuration to use production defaults. Implemented dynamic endpoint resolution for better environment handling. Improved reliability for production deployments.
72 +
73 +**Auth0 Toolkit** - Replaced hardcoded endpoints with dynamic tenant-based URL resolution. Supports multi-tenant deployments without manual configuration. Automatically constructs the correct endpoint based on the tenant configuration.
74 +
75 +#### Endpoint Fixes
76 +
77 +**DataScope Toolkit** - Fixed the Get Current User Endpoint to use the correct API path. Resolves authentication verification issues.
78 +
79 +**D2L Brightspace Toolkit** - Updated the Get Current User Endpoint to match the latest API specifications. Ensures proper user identification and session validation.
80 +
81 +### Migration Guide
82 +
83 +For toolkits with breaking changes, please update your configurations as follows:
84 +
85 +1. **Make**: Replace Region with the full Base URL (e.g., `https://us-east-1.make.com`)
86 +2. **Bubble**: Replace Subdomain with the full Base URL (e.g., `https://myapp.bubbleapps.io`)
87 +
88 +For deprecated authentication methods:
89 +- **HelloBar & FormSite**: Generate new API keys from your account settings and update your authentication configuration
fumadocs/lib/source.ts
+12 -1
@@ -1,4 +1,4 @@
1 -import { docs } from 'fumadocs-mdx:collections/server';
1 +import { docs, changelog } from 'fumadocs-mdx:collections/server';
2 import { type InferPageType, loader } from 'fumadocs-core/source';
3 import { lucideIconsPlugin } from 'fumadocs-core/source/lucide-icons';
4
@@ -9,6 +9,8 @@ export const source = loader({
9 plugins: [lucideIconsPlugin()],
10 });
11
12 +export const changelogEntries = changelog;
13 +
14 export function getPageImage(page: InferPageType<typeof source>) {
15 const segments = [...page.slugs, 'image.png'];
16
@@ -25,3 +27,12 @@ export async function getLLMText(page: InferPageType<typeof source>) {
27
28 ${processed}`;
29 }
30 +
31 +export function formatDate(dateStr: string): string {
32 + // Add T12:00 to avoid UTC midnight timezone shift
33 + return new Date(`${dateStr}T12:00:00`).toLocaleDateString('en-US', {
34 + year: 'numeric',
35 + month: 'long',
36 + day: 'numeric',
37 + });
38 +}
fumadocs/mdx-components.tsx
+5
@@ -2,6 +2,8 @@ import defaultMdxComponents from 'fumadocs-ui/mdx';
2 import type { MDXComponents } from 'mdx/types';
3 import { YouTube } from '@/components/youtube';
4 import { Tabs, Tab, TabsList, TabsTrigger, TabsContent } from 'fumadocs-ui/components/tabs';
5 +import { Accordion, Accordions } from 'fumadocs-ui/components/accordion';
6 +import { Callout } from 'fumadocs-ui/components/callout';
7 import { ProviderCard, ProviderGrid } from '@/components/provider-card';
8 import {
9 Key,
@@ -23,6 +25,9 @@ export function getMDXComponents(components?: MDXComponents): MDXComponents {
25 TabsList,
26 TabsTrigger,
27 TabsContent,
28 + Accordion,
29 + Accordions,
30 + Callout,
31 ProviderCard,
32 ProviderGrid,
33 // Lucide icons - available globally in MDX without imports
fumadocs/source.config.ts
+10
@@ -1,9 +1,11 @@
1 import {
2 defineConfig,
3 defineDocs,
4 + defineCollections,
5 frontmatterSchema,
6 metaSchema,
7 } from 'fumadocs-mdx/config';
8 +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
@@ -20,6 +22,14 @@ export const docs = defineDocs({
22 },
23 });
24
25 +export const changelog = defineCollections({
26 + type: 'doc',
27 + dir: 'content/changelog',
28 + schema: frontmatterSchema.extend({
29 + date: z.string(),
30 + }),
31 +});
32 +
33 export default defineConfig({
34 mdxOptions: {
35 // MDX options