Unified MCP Client Library for Elixir

Created By
ramonlimaramosa year ago
🌐 Mcpixir is the open source way to connect any LLM to any MCP server and build custom agents that have tool access, without using closed source or application clients.
Overview

What is Mcpixir?

Mcpixir is an open-source library designed to connect any Large Language Model (LLM) to any MCP (Multi-Channel Protocol) server, enabling the creation of custom agents with tool access without relying on closed-source applications.

How to use Mcpixir?

To use Mcpixir, add it to your Elixir project's dependencies and configure your preferred LLM provider with the necessary API keys. You can then create an MCP client and agent to run queries.

Key features of Mcpixir?

  • Ease of use: Create an MCP-capable agent with just 6 lines of code.
  • LLM Flexibility: Compatible with any LLM that supports tool calling (e.g., OpenAI, Anthropic).
  • Dynamic Server Selection: Agents can choose the most suitable MCP server for tasks.
  • Multi-Server Support: Connect to multiple MCP servers simultaneously.
  • Tool Restrictions: Control access to potentially dangerous tools.

Use cases of Mcpixir?

  1. Web browsing with Playwright.
  2. Searching for accommodations on Airbnb.
  3. Creating 3D models in Blender.
  4. Running complex queries that utilize multiple tools from different servers.

FAQ from Mcpixir?

  • Can Mcpixir connect to any LLM?
    Yes, it works with any LLM that supports tool calling.
  • Is Mcpixir free to use?
    Yes, Mcpixir is open-source and free to use.
  • What are the requirements for using Mcpixir?
    You need Elixir 1.15+, Erlang/OTP 25+, and access to an MCP implementation.
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ramonlimaramos
Star
1
Language
Elixir
License
MIT 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)

20 hours ago
Gpt Scrambler

2 days ago