MCP servers that ship as code — a repository or a package you install and run locally (usually over stdio). They have no hosted endpoint, so we cannot probe or grade them: instead each one shows its repository, install command, license, stars and when it was last updated.
Collected from GitHub repositories and npm, PyPI, Cargo, Go, Maven, NuGet and RubyGems packages tagged as MCP servers, the official MCP Registry, Docker's MCP catalog, ModelScope, Baidu MCP World, Cline and other public directories; one entry per repository. A server that also offers a hosted endpoint is listed under Remote instead. These entries are not counted in our reachability, verification or readiness statistics.
-
MCP Server for AIPost.email — typed, structured messaging for AI agents with Ed25519 identities
npm MIT -
agentic-commgithub.com/agentralabs/agentic-commupdated this year
Structured agent-to-agent and agent-to-human communication — channels, pub/sub, message routing, and presence. One .acomm file. Rust core + MCP server.
cargo MIT ★ 5 -
LinkedIn for AI assistants (MCP) — profiles, people/job/company search, feed & messaging as structured JSON, plus gated writes (connect/message/post/react/comment) via LinkedIn's API instead of DOM-clicking. Stealth-browser engine, 24 tools, built-in safety layer. Claude · Cursor · any MCP client.
npm MIT ★ 12 -
wireforge-coregithub.com/hanmahong5-arch/wireforge-coreupdated this year
Local-first toolkit for financial wire messages: SR2026 structured-address CI gate, MT/MX truncation detector, ISO 8583 codec, migration regression evidence. CLI + 12 read-only MCP tools.
mcpb Apache-2.0 -
outbound-engine-mcpgithub.com/closermethod/outbound-engine-mcpupdated this year
Outbound Engine MCP for AI agents and creators. One cold-outreach engine, any target: brand deals, UGC, newsletter sponsorships, jobs, podcasts. HOOK/BRIDGE/SOFT-ASK structuring, message auditing, follow-up ladder, reply playbook, red-flag detection.
-
Invite-based channels for AI agents to collaborate across machines: realtime messaging, structured agent contracts, per-side human approvals, MCP + single-file CLI, self-hostable.
npm MIT ★ 1 -
Oktopost-MCPgithub.com/Oktopost/Oktopost-MCPupdated this year
The Oktopost MCP Server provides an AI-ready interface to the Oktopost REST API, enabling secure, structured access to campaigns, messages, posts, media, workflows, and advocacy tools. It serves as a reference implementation and a starting point for building custom MCP integrations with Oktopost.
-
im-connectoractive
MCP server that lets agents drive DingTalk (dws) and WeCom (wecom-cli) CLIs: send messages, write reports, create todos, query calendars and approvals. Ships MCP resources, server instructions, structured tool output, and an inline QR login row for the DS
npm MIT -
A protocol-driven RAG system that decouples LLM reasoning from tool execution using MCP, enabling scalable document intelligence with ChromaDB and OpenAI. Implements an MCP client–server architecture with explicit message orchestration, structured tool execution, and stateful multi-turn memory for document-grounded LLM applications
-
AYLENTO · 艾伦兔no update data
# AYLENTO · 艾伦兔 Connect Agents across AI clients using independent identities, private messages, group chats, attachments, follows and block lists. 艾伦兔为不同 AI 客户端中的 Agent 提供独立身份和通信能力,共 36 个 MCP 工具。 Client 0.13.0-beta.4 public beta; MCP runtime 0.13.0-beta.1. 本包为公测版,普通用户注册无需邀请码。 ## Install / 安装 This is a **local stdio MCP bundle**, not a hosted HTTP endpoint. Import the `.mcpb` file into a compatible client. The client must supply **Node.js 24.15.0 or newer**; the bundle includes the JavaScript server and its dependencies, but does not include Node itself. Older bundled Node runtimes cannot run it. No npm installation or API key is required for this bundle. 在支持 MCPB 的客户端导入安装包,并确保它实际使用 Node.js 24.15.0 或更新版本。包内含完整 JS 客户端和依赖,不含 Node 运行环境。安装时为当前客户端选择独立的本地配置名称(默认 `smithery-local`)。 For clients without MCPB import, extract this archive to a permanent directory and configure a local MCP server with command `node`, argument `/absolute/path/to/extracted/bin/aylento.mjs`, and environment `AYLENTO_BASE_URL=https://aylento.com`, `AYLENTO_PROFILE=your-unique-host-profile`. Windows uses an absolute Windows path. Each host's JSON structure differs; see the [official installation guide](https://github.com/popularzb/aylento-plugins/blob/v0.13.0-beta.4/README.md). Do not enable duplicate native-plugin and manual-MCP installations for the same identity. ## Pair and use / 配对与使用 1. Register at [aylento.com](https://aylento.com) and create a separate Agent Chat for this host. 2. Ask: “查看我的艾伦兔连接状态,未连接才开始配对。” The Agent should call `aylento_connection_status` first and `aylento_connect` only when disconnected. 3. Personally approve the returned pairing page and code in your browser. Never paste passwords, session tokens or private pairing links into public listings or issues. 4. Ask the Agent to call `aylento_finish_connection` once after approval. Pending means wait for the person, not continuous polling. 5. Ask “查看我的艾伦兔新消息” or “查看当前身份的黑名单”. To send, specify the recipient's exact rabbit ID and the message; verify the recipient before sending. Use both a separate profile **and a separate Agent Chat** per host. A profile only isolates local storage; it does not create a server identity. Pairing an existing identity elsewhere replaces its prior external session. Keep the same profile during an upgrade to retain local authorization and history. The included `skills/aylento/SKILL.md` contains model-facing instructions. MCPB hosts do not necessarily load skills automatically; follow the host's instructions to load it if supported. Codex, Claude Code and Gemini CLI also have [native installation options](https://github.com/popularzb/aylento-plugins/blob/v0.13.0-beta.4/README.md). ## Data and behavior / 数据与行为 Messages are sent through the AYLENTO service. Incoming message history and attachments are saved to local SQLite before delivery acknowledgment; histories do not automatically synchronize between devices. Tool results may enter the selected host/model's context and logs. Read `PRIVACY.md` for destinations and retention details. Before mutual following or the first reply, only one unsolicited private message is permitted. Once the recipient replies, both parties may continue; blocking and rate limits still apply. `REPLY_REQUIRED` means the message was not sent. Reception is not permission to auto-reply, and receiving messages does not guarantee the host wakes a model. Local reception stops when the process or device stops. If a send has an unknown outcome, inspect messages before attempting again. Disconnecting revokes external authorization but retains local history. Uninstalling the bundle does not erase that history. Do not share actual state directories, credentials, messages or attachments in bug reports. The bundle is checked with isolated MCP startup and a 36-tool inventory. This is not a claim of completed real-model messaging tests in every host or on every operating system. Refer to [host verification scope](https://github.com/popularzb/aylento-plugins/blob/v0.13.0-beta.4/HOSTS.md). ## Copyright and updates / 版权与更新 Copyright (c) 2026 AYLENTO copyright holders. All rights reserved. **AYLENTO Client Use License v1.0** applies; see `LICENSE.txt`. This is not MIT or another open-source license. Personal and organizational internal installation and use are allowed; additional program modification, repackaging, external redistribution, resale and sublicensing require separate written permission. Third-party licenses, statutory rights and rights already granted by official platform terms remain unaffected. Keep `THIRD_PARTY_NOTICES.md` with the bundle. Download updates only from official AYLENTO channels, preserve the profile and local data, and install a newer bundle through your host. Merely pushing Git does not update an installed bundle or publish a Smithery release; the distribution build and authenticated publication must also run. [Website](https://aylento.com) · [Official repository](https://github.com/popularzb/aylento-plugins) · [Release downloads](https://github.com/popularzb/aylento-plugins/releases) · [Public support](https://github.com/popularzb/aylento-plugins/issues)
smithery -
Fashion E-Commerce Intelligencegithub.com/alexgenovese/ecommerce-fashion-market-analysisno update data
# Fashion E-Commerce Intelligence MCP Server Empower your AI agents, copilots, and assistants with vertical domain-specific fashion intelligence. Built by [alexgenovese.com](https://alexgenovese.com), this Model Context Protocol (MCP) server provides automated **SEO auditing, category trend research, DTC demand forecasting, CRM segment enrichment, and campaign creative generation**—designed natively for Cursor, Claude Desktop, Claude Code, and any MCP-compatible environment. --- ## ⚡ What It Does | Capability | Without this server | With Fashion MCP | |---|---|---| | **SEO Auditing** | Manual checklists, generic advice | Automated **0-100 score** across 5 dimensions with fashion-specific validation (fit, material, color, season, schema, OG, Twitter Cards). | | **Trend Research** | Generic search queries | Deep category-level trend intelligence (trending keywords, colors, silhouettes, price tiers, market fit, confidence). | | **Demand Forecasting** | Spreadsheets & gut feel | Explainable weighted-rule forecast model: `baseline × trend × media × retention × inventory × seasonality` with backtesting. | | **CRM Segment Enrichment** | Static email lists | Customer segments enriched with trending colors/silhouettes/keywords, audience clusters, and ready-to-send targeted messaging. | | **Campaign Creative** | Standard copywriters per channel | Platform-specific campaign themes, hooks, value propositions, and ready-to-use creative briefs grounded in real-time trend data. | --- ## 🔧 Exposed Tools - `product_seo_audit`: Audit any fashion product listing for SEO best practices, structured schema, meta tags, and fashion relevance (fit, size, material). - `fashion_trend_analysis`: Analyze fashion trend data mapped from search engine and social media queries. *(Receives search data input seamlessly, no API key required)*. - `fashion_category_demand_outlook`: Get a rapid, light demand pulse check for a specific product category in a target market and season. - `fashion_dtc_forecast_analysis`: Generate complete DTC demand forecasts with scenario planning (base/upside/downside) and stock-out/overstock risk analysis. - `fashion_customer_trend_enrichment`: Map trending keywords, colors, and silhouettes onto existing CRM customer segments for targeted email/SMS campaigns. - `fashion_campaign_theme_recommendation`: Recommend conversion-optimized ad campaign themes, hooks, and creative briefs for Meta, Google, TikTok, or Email. --- ## 🔐 Privacy & Technical Features - **No API Keys Required:** All analysis, SEO audits, demand forecasts, and CRM enrichment tools run locally with the data you supply. Upstream search data for `fashion_trend_analysis` uses your existing Tavily MCP server. - **Explainable Outputs:** Every tool returns explicit `assumptions[]`, `dataGaps[]`, and `confidence` scores, so your agent always understands the reasoning behind recommendations. - **Zero-Config Local Cache:** Uses a local SQLite persistence layer (`~/.fashion-mcp/store.db`) to cache snapshots, feature stores, and forecast actuals for backtesting. ## 💻 Local Installation To install this stdio-based server locally via Smithery: ```bash npx smithery install alexgenovese/ecommerce-fashion-market-analysis ```
smithery -
Let your Claude Code sessions talk over NATS. Orchestrate repo-level agents with pub/sub, durable queues, and structured results.
MIT