Cortex

Created By
FreePeaka year ago
A declarative platform for building Model Context Protocol (MCP) servers in Golang—exposing tools, resources & prompts in a clean, structured way
Overview

What is Cortex?

Cortex is a declarative platform for building Model Context Protocol (MCP) servers in Golang, designed to expose tools, resources, and prompts in a structured manner.

How to use Cortex?

To use Cortex, install it via Go with the command go get github.com/FreePeak/cortex, and follow the quickstart guide to create your MCP server.

Key features of Cortex?

  • Implements the full MCP specification for standardized context provision.
  • Supports multiple transport methods including STDIO and HTTP with Server-Sent Events (SSE).
  • Allows for easy creation and management of tools and resources.
  • Provides a plugin system for extending server capabilities.

Use cases of Cortex?

  1. Building custom MCP servers for various applications.
  2. Exposing computational tools for LLMs.
  3. Creating providers to group related tools and resources.

FAQ from Cortex?

  • What is the Model Context Protocol (MCP)?

MCP is a standardized protocol that allows applications to provide context for LLMs efficiently.

  • Is Cortex free to use?

Yes! Cortex is open-source and available under the Apache License 2.0.

  • How can I contribute to Cortex?

Contributions are welcome! You can fork the repository and submit a pull request.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
FreePeak
Star
9
Language
Go
License
Apache-2.0 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago