MCP server for Surface — one tool, `surface`, that shows the user files, URLs, or HTML the agent just wrote.
Surface MCP SDK
User-equivalent Odoo access for AI agents via MCP
Lightweight core CLI surface for Claude Flow — memory + hooks commands only. Designed to load fast on cold npx cache (<5s) so plugin skills don't race the 30s MCP-startup timeout. The full @claude-flow/cli metapackage lazy-loads everything else on top of
The Material Components for the web menu surface component
Model Context Protocol server for Paperclip.
Atlas catalog graph data, SDK, and CLI.
Node and Bun local Prisma Streams runtime for trusted development workflows.
Model Context Protocol server for Paperclip.
Launcher package for the DeltaScope MCP stdio server
Framework for rapidly creating high quality, server-side node.js applications, using plugins like building blocks
The Material Components for the web Ink Ripple effect for web element interactions
Unified CLI surface for h2a hosts and MCP-oriented coordination flows.
Playwright Tools for MCP
MCP server exposing the Caelo CMS chat-runner as a `caelo_chat` tool. Lets Claude Code (or any MCP-aware client) drive a Caelo install from outside the browser.
Model Context Protocol implementation for TypeScript
A TypeScript SSE proxy for MCP servers that use stdio transport.
MCP server bridging Claude Code / Cursor / OpenClaw to Susurration
Help agents automatically write and test stories for your UI components
The official TypeScript library for the Cloudflare API
A high-level API to control headless Chrome over the DevTools Protocol
AI-powered access to Attio CRM. Manage contacts, companies, deals, tasks, and notes. Search records, update pipelines, and automate workflows for sales and GTM teams.
1K4 Claude Code Bridge — one install, every tool. Plan review, advisors, brainstorm, and the Studio Lab bridge.
MCP server for Chrome DevTools
Igniter provides a contracts-native embedded kernel, extension packs, local application runtime, web runtime, cluster runtime, and MCP adapter surfaces without shipping archived legacy layers.
pikuri-mcp adds Model Context Protocol support to pikuri-core agents: a +Pikuri::Mcp::Registry+ for declaring stdio + HTTP MCP servers, the +Pikuri::Mcp::Servers+ runtime that spawns them, a +Pikuri::Mcp::Synthesizer+ that LLM-fills missing server descriptions, a +Pikuri::Mcp::Verifier+ that screens server surfaces for prompt-injection patterns before any tool is advertised to the LLM, and a +Pikuri::Mcp::Extension+ that wires everything into a +Pikuri::Agent+ via +c.add_extension(...)+ in the +Agent.new+ block.
Rails-AI-Bridge introspects your Rails application and exposes structure to AI assistants via static context files and a live Model Context Protocol (MCP) server. It classifies Active Record models semantically (Core, Join, Supporting), optionally surfaces non-ActiveRecord Ruby classes under app/models (tagged POJO/Service), and integrates with editors and assistants such as Claude, Gemini, Cursor, and Windsurf.
pikuri-core is the lean, audit-friendly foundation of the pikuri family: Pikuri::Agent (a thin wrapper around ruby_llm's chat loop) with its Configurator + Extension protocol, the strict Pikuri::Tool framework, a listener surface for rendering / budgets / sub-agents, and four bundled stateless tools (calculator, web search, web scrape, fetch). Extensions (skills, MCP, workspace, coding stack, named-agent personas) live in sibling gems so a privacy-conscious user can install just this core and audit a minimal dependency tree. For the convenience bundle that pulls in everything, see the +pikuri+ metagem.
+pikuri+ is the convenience bundle for the pikuri AI-assistant toolkit. It ships no Ruby code of its own beyond a tiny entry file that +require+'s each sibling gem; +gem install pikuri+ pulls in pikuri-core, pikuri-extractors, pikuri-pdf, pikuri-skills, pikuri-tasks, pikuri-memory, pikuri-workspace, pikuri-code, pikuri-mcp, pikuri-subagents, pikuri-vectordb, and pikuri-assistant in one shot, and +require 'pikuri'+ boots all of them. Privacy-conscious users who want a minimal dependency tree to audit should install +pikuri-core+ directly and opt into the extension gems they actually need — same +bundle add+ pattern Rails users have always had. See each pikuri-* gem's README for its individual surface.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.