# Glypse MCP server

> Scan prediction markets on Polymarket and Kalshi and draw on analyzed social posts and research for trading decisions.

- Listing: https://mcp.tc/i/glypse
- Connect: use the server's own URL `https://mcp.glypse.ai` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Data & Analytics](https://mcp.tc/c/analytics)
- Vendor: Glypse
- Homepage: <https://glypse.ai/>

## About

Glypse connects an AI assistant to prediction market analytics and event research. It helps an agent scan large numbers of markets on Polymarket and Kalshi and draw on analyzed social posts, research pages and sentiment data without piecing it together one post at a time.

The server runs as a hosted streamable HTTP endpoint at https://mcp.glypse.ai. Users create a free Glypse account and complete browser-based OAuth sign-in before connecting. The granted scope is read-only (mcp:read).

## What it can do

- Scan prediction markets across Polymarket and Kalshi
- Pull event research pages with sourced context
- Analyze social media posts and sentiment around events
- Find related events on both venues

## Example prompts

- "Scan open prediction markets and list the ones with the most social activity this week."
- "Summarize the bull and bear cases for the Anthropic valuation market."
- "Find related Polymarket and Kalshi events for this election market."
- "What is the social sentiment around this prediction market?"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http glypse https://mcp.glypse.ai
```

2. Start Claude Code, type `/mcp`, pick **glypse** and choose **Authenticate**. A browser window opens for the Glypse sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **Glypse** and paste this URL:

```url
https://mcp.glypse.ai
```

3. Click **Add**, then **Connect**, and sign in when Glypse asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Glypse&connectorUrl=https%3A%2F%2Fmcp.glypse.ai>) (opens connector settings)

2. Check that the URL reads `https://mcp.glypse.ai` and click **Add**.

3. Click **Connect** and sign in when Glypse asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://mcp.glypse.ai` as the server URL, then for authentication choose **OAuth**. ChatGPT sends you to Glypse to sign in.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=glypse&config=eyJ1cmwiOiJodHRwczovL21jcC5nbHlwc2UuYWkifQ%3D%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "glypse": {
      "url": "https://mcp.glypse.ai"
    }
  }
}
```

Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=glypse&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.glypse.ai%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"glypse","type":"http","url":"https://mcp.glypse.ai"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "glypse": {
      "type": "http",
      "url": "https://mcp.glypse.ai"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "glypse": {
      "serverUrl": "https://mcp.glypse.ai"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add glypse --url https://mcp.glypse.ai
codex mcp login glypse
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.glypse]
url = "https://mcp.glypse.ai"
```

### Gemini CLI

```bash
gemini mcp add --transport http glypse https://mcp.glypse.ai
```

Then, inside Gemini CLI, run `/mcp auth glypse` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "glypse": {
      "type": "http",
      "url": "https://mcp.glypse.ai"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.glypse.ai`.

## Details

- Last checked: 2026-11-15 (reachable, asks for credentials)
- Listed: 2026-11-04
- Updated: 2026-11-04

---
Source: https://mcp.tc/i/glypse (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report