Skip to content

Your agent. Your workspace.

Connect through MCP, sign in once, and bring source-backed research into the tools you already use.

Integrations

One connection. A real first result.

Add the server, sign in and approve, then verify your workspace connection. No key to copy for an OAuth-capable agent.

Integrations

Montage for Claude Code

Connect Montage's social media research MCP server to Claude Code. Follow the setup command, authorize your workspace and verify search and watchlist tools.

Read guide
Integrations

Montage for Claude Desktop

Bring source-backed research, watchlists and audiences into Claude Desktop through MCP.

Read guide
Integrations

Montage for Cursor

Add Montage's social media research MCP server to Cursor. Configure the HTTP endpoint, authorize your workspace and verify source-backed research tools.

Read guide
Integrations

Montage for ChatGPT

Connect Montage to ChatGPT for social media research through MCP. Check workspace policy, authorize access and verify your first source-backed tool response.

Read guide
Integrations

Montage for VS Code

Bring source-backed research, watchlists and audiences into VS Code through MCP.

Read guide
Integrations

Montage for Codex

Configure Montage in Codex CLI or the IDE, complete remote OAuth, and verify workspace access with a read-only signals_status call.

Read guide
Integrations

Montage for Gemini CLI

Add Montage through Gemini CLI's Streamable HTTP settings, check the applicable OAuth controls, and verify authorized workspace status.

Read guide
Integrations

Montage for Cline

Register Montage as a remote Streamable HTTP server in Cline, authorize through its supported controls, and test read-only workspace status.

Read guide
Integrations

Montage for Roo Code

Check Roo Code's project overrides and remote transport, confirm a supported authorization path, then validate Montage with signals_status.

Read guide
Integrations

Montage for Continue

Load Montage in Continue's Agent-mode MCP configuration, resolve version-specific authorization, and check workspace access without writes.

Read guide
Integrations

Montage for Zed

Add Montage to Zed Agent as a remote MCP server, follow its OAuth prompt, and distinguish editor settings from external agent configuration.

Read guide
Integrations

Montage for OpenCode

Use OpenCode's v2 remote MCP server layout, complete sign-in through /mcps, and verify the selected Montage workspace with signals_status.

Read guide
Integrations

Montage for Warp

Configure Montage as a URL-based Streamable HTTP server in Warp, check current authentication support, and validate a read-only response.

Read guide
Integrations

Montage for LM Studio

Review LM Studio's remote MCP configuration and explicit authentication limitations before attempting an authorized Montage status check.

Read guide
Integrations

Montage for LangChain

Plan a version-qualified LangChain MCPAdapter connection to Montage, configure application-owned auth, and check status without a model call.

Read guide
Integrations

Montage for OpenAI Agents SDK

Choose local Streamable HTTP control or hosted MCP in the OpenAI Agents SDK, separate auth responsibilities, and validate Montage read-only.

Read guide
Integrations

Montage for Pydantic AI

Use Pydantic AI's current MCPToolset and configured FastMCP authorization to reach Montage, then validate status before running an agent.

Read guide
Integrations

Montage for LlamaIndex

Connect LlamaIndex's HTTP MCP client to Montage with application-owned auth, filter discovery, and distinguish a tool list from status proof.

Read guide
Integrations

Montage for Semantic Kernel

Use Semantic Kernel's documented Python Streamable HTTP plugin for Montage, manage its async lifetime, and verify authorized read-only status.

Read guide
Integrations

Montage for MCP Inspector

Use an already-installed MCP Inspector to diagnose Montage's HTTP transport and authorization, then issue a bounded read-only signals_status call.

Read guide
Integrations

Montage for FastMCP

Configure a FastMCP remote Client with approved OAuth, manage its async lifetime, and validate Montage directly through signals_status.

Read guide
Integrations

Montage for the MCP Python SDK

Use the official Python SDK's version-qualified Client API for Montage, supply application-owned authorization, and test read-only status.

Read guide
Integrations

Montage for the MCP TypeScript SDK

Match Montage setup to the official TypeScript SDK's v2 client split or supported v1 API, then verify authorized Streamable HTTP status.

Read guide
Integrations

Montage for the MCP Go SDK

Plan a fail-closed Montage client with the official Go MCP SDK, account for experimental OAuth limits, and validate authorized read-only status.

Read guide

Know what social media shows about you.
Start with a question.

Get started
montage