Koskamo

Historis MCP MCP server

An event-based CRM that allows AI assistants to read business history and write signed, dated entries. It supports managing organizations, persons, events, tags, and rules, enabling agents to track contacts, update statuses, and apply organizational playbooks.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

OAuth sign-inEndpoint checked 2026-10-05Operated by Historis
MCP endpoint (Streamable HTTP)
https://api.historis.app/mcp
Vendor documentation

What you can do with it

  • Read organization context and daily briefs
  • Create and update events with statuses
  • Manage persons and link them to events
  • Apply organizational rules for tagging and routing

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http historis-mcp https://api.historis.app/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add historis-mcp --url https://api.historis.app/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable historis-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "historis-mcp": {
      "url": "https://api.historis.app/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.
Cline configuration
{
  "mcpServers": {
    "historis-mcp": {
      "type": "streamableHttp",
      "url": "https://api.historis.app/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start historis-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "historis-mcp": {
      "type": "http",
      "url": "https://api.historis.app/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http historis-mcp https://api.historis.app/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "historis-mcp": {
      "url": "https://api.historis.app/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "historis-mcp": {
      "serverUrl": "https://api.historis.app/mcp"
    }
  }
}

Do you run Historis MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing