Skip to content

Your tools, through MCP.In Chippi’s working context.

Connect a supported remote MCP server so agents can use the tools it exposes. Keep the server, authentication and agent access explicit.

Read the documentation
Chippi

How the connection fits.

  1. 01

    Your service

    A supported remote server exposes tools through its HTTPS endpoint.

  2. 02

    Chippi’s connection

    Configure authentication, discover tools and choose agent access.

  3. 03

    A defined task

    Use the available tools within their permissions and confirmation settings.

This describes Chippi as a client of remote MCP servers. A local stdio server uses a different setup; it is not a remote HTTPS connection.

Choose how your server connects.

Chippi supports three MCP transports. Choose the one your server provides. The tools come from that server and appear after discovery.

Streamable HTTP

Connect a remote MCP server using its HTTPS endpoint.

View connection

Server-sent events

Connect a remote MCP server that uses the SSE transport.

View connection

Local STDIO

Configure a command-based MCP server on the Chippi host.

View connection

A server. Its tools.A clear connection.

Chippi connects as an MCP client. These public TypeScript SDK v1 examples show the same connection, discovery and tool-call flow. Use your provider’s endpoint and credentials.

For Node.js with @modelcontextprotocol/sdk 1.30.0.

TypeScript · SDK v1
import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StreamableHTTPClientTransport } from
  "@modelcontextprotocol/sdk/client/streamableHttp.js";
import type { Tool } from "@modelcontextprotocol/sdk/types.js";

const endpoint = process.env.MCP_SERVER_URL;
if (!endpoint) throw new Error("Set MCP_SERVER_URL");

const token = process.env.MCP_ACCESS_TOKEN;
const client = new Client({ name: "mcp-example", version: "1.0.0" });
const transport = new StreamableHTTPClientTransport(new URL(endpoint), {
  requestInit: {
    headers: token ? { Authorization: "Bearer " + token } : {},
  },
});
await client.connect(transport);

Start a client session with your provider’s MCP endpoint.

  • Use the endpoint supplied by your server provider.
  • This example accepts an existing bearer token. OAuth authorization is handled separately.

Work with your existing services.

A remote MCP connection brings external tools into Chippi. It is separate from adding a workspace app or connecting a service through the integration catalog.

Explore integrationsAsk your own agent about Chippi

Before the first task

  • Confirm the server address and provider.
  • Authorize the account and required scopes.
  • Check discovered tools and agent access.
  • Review confirmation settings for external actions.
Read about access and controls

This website uses necessary browser storage to remember your choice. Analytics and advertising services are not currently connected.

Strictly necessary

Remembers this choice for 180 days on this browser and website.

Always active

Analytics

No analytics integration is running on this website.

Not in use

Marketing

No advertising or cross-site marketing integration is running here.

Not in use

Cookie PolicyPrivacy Policy

These settings do not apply to the signed-in Chippi app or block externally hosted fonts and images. See the details.