@devries-cameron20 / composio Mirror · read-only / commits / f61fce506
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.

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 21, 11:00 UTC

docs: update documentation for new changelog entries (#4493)

## Summary Automated documentation updates triggered by new changelog entries merged to next. Generated by Codex via GitHub Actions. Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

sdkrelease[bot] committed Sep 22, 2026 at 19:00 UTC f61fce506d3437a1116cbe96cc4d2ae1843f27a4
3 files changed +12
docs/content/docs/configuring-sessions.mdx
+9
@@ -26,6 +26,15 @@ By default, a session has access to every toolkit in the Composio catalog. Your
26
27 You can also attach local custom tools and custom toolkits that run in-process alongside Composio tools. See [Custom tools and toolkits](/docs/extending-sessions/custom-tools-and-toolkits).
28
29 +### API key permissions
30 +
31 +If you use a [scoped project API key](/reference/authenticating-to-composio/project-api-key-permissions), grant permissions for the session operations your application needs:
32 +
33 +- **Session management** controls creating, viewing, configuring, and deleting sessions. It does not grant tool execution access.
34 +- **Session tool execution** covers search, tool execution, proxy execution, and session-linked MCP access.
35 +
36 +Enable both permissions if your application manages sessions and executes tools through them.
37 +
38 ## Enabling toolkits
39
40 To limit a session to specific toolkits, pass an array of toolkit slugs. The agent can only discover and use tools from these toolkits.
docs/content/docs/security/overview.mdx
+1
@@ -14,6 +14,7 @@ Composio is SOC 2 Type II compliant. For our latest reports and certifications (
14
15 - Organizations and projects isolate your resources. Data from one project is not visible to another.
16 - API keys are scoped, support per-key IP allowlisting, and can opt in to capabilities such as Proxy Execute at creation.
17 +- Scoped project API keys separate **Session management** (creating, viewing, configuring, and deleting sessions) from **Session tool execution** (search, tool execution, proxy execution, and session-linked MCP access). See [API key permissions](/reference/authenticating-to-composio/project-api-key-permissions) to configure access.
18 - Multi-factor authentication (MFA) is available for Dashboard sign-in and can be enforced by an organization admin.
19
20 ## Credential protection
docs/content/docs/sessions-via-mcp.mdx
+2
@@ -18,6 +18,8 @@ Want to bring tools from your own remote MCP server into Composio instead? See [
18
19 ## The MCP endpoint
20
21 +If you use a scoped project API key, enable **Session management** to create and configure sessions and **Session tool execution** for session-linked MCP access. See [API key permissions](/reference/authenticating-to-composio/project-api-key-permissions) for access levels and routes.
22 +
23 Opt into MCP by passing `mcp: true` when you create the session. The session then exposes its hosted MCP server. Read the URL and headers off `session.mcp`:
24
25 <Tabs groupId="language" items={['Python', 'TypeScript']} persist>