From October 1, WhatsApp charges for every business reply. Read the migration playbook →

AI agents

Connect SuperCognit to Goose

Goose adds MCP servers as extensions, including remote ones over streamable HTTP. Add your SuperCognit workspace and Goose can create and edit agents, build knowledge bases, attach tools and read conversations — from the desktop app or the CLI.

Connection details

# ~/.config/goose/config.yaml
extensions:
  supercognit:
    enabled: true
    type: streamable_http
    name: supercognit
    uri: https://mcp.supercognit.com/platform/<workspace>/mcp
    headers:
      x-api-key: <api-key>

Replace <workspace> with the workspace slug shown under Integrations → Platform MCP, and <api-key> with a workspace API key when your client does not sign in with OAuth. Published MCP servers connect the same way at their own URL.

What you can do once it's connected

Recipes that manage agents

Turn "refresh the docs knowledge base and summarise this week's conversations" into a Goose recipe you run on a schedule.

Knowledge from local files

Goose reads your folders and pushes documents into a SuperCognit knowledge base.

Tools for internal services

Register internal endpoints as SuperCognit tools so an internal agent can call them.

Usage reports

Ask for conversations, leads and credit usage and have Goose write the report where you need it.

How to connect

01

1. Copy your workspace MCP URL

Integrations → Platform MCP in the dashboard. One URL per workspace.

02

2. Add a remote extension

Run goose configure → Add Extension → Remote Extension (Streaming HTTP), name it supercognit and paste the URL — or add the extension to config.yaml.

03

3. Add a workspace API key

Set an x-api-key header on the extension with a key from Integrations → API.

04

4. Run a session

Start Goose; the SuperCognit tools are available in every session where the extension is enabled.

Frequently asked questions

Both read the same config, so one setup covers both.

Use a key for a reliable setup across Goose versions; if yours supports OAuth for remote extensions, that works as well.

Reference an environment variable where Goose supports it, or keep the file per user and out of version control.

Goose is the builder's tool; the customer-facing agent runs on SuperCognit with its own channels, guardrails and billing.

Your workspace, one MCP URL away

Create a workspace, copy the MCP URL from Integrations → Platform MCP, paste it into your agent — free for 7 days.

Start building