Open Enterprise AI MCP Server
OfficialEnables interaction with Elasticsearch for searching and analyzing data.
Adds tools for managing GitHub repositories, issues, pull requests, and code search.
Provides access to Gmail for reading and sending email through OAuth.
Adds tools for managing files and folders on Google Drive, including listing, reading, creating, and searching.
Provides access to HubSpot CRM to manage contacts and other CRM data.
Provides tools for interacting with Jira issues and projects.
Provides a query tool for running MongoDB queries and aggregations.
Provides a tool to run SQL queries against a MySQL database, allowing interaction with tables and data.
Provides a tool to run SQL queries against a PostgreSQL database, allowing interaction with tables and data.
Enables interaction with Redis for data retrieval and management.
Adds tools for Slack channel management, message posting, and reading conversations.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Open Enterprise AI MCP ServerQuery the postgres connector for the top 10 customers by revenue."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Connect any AI coding assistant to your enterprise data — databases, files, APIs, and more — via a single binary.
What is OE MCP Server?
OE MCP Server is a standalone binary that implements the Model Context Protocol (MCP) and exposes your enterprise data sources as tools that AI apps can use directly.
Connect Claude Code, Cursor, Windsurf, or Claude Desktop to your PostgreSQL database, local filesystem, GitHub, Slack, Google Drive, SSH servers, and more — without writing any integration code.
No code. Define connectors in a single YAML file.
45+ connector categories. 2,600+ enterprise systems supported out of the box.
Two transport modes.
--stdiofor Claude Code VS Code / desktop apps;--servefor Cursor, Windsurf, and cloud deployments.Persistent memory. Built-in
memory_set / memory_get / memory_list / memory_deletetools — context survives across sessions.Self-hosted. Runs on your own machine. No cloud dependency. Own your data.
Related MCP server: ContextStream MCP Server
Quick Start via npm (Recommended)
No binary download needed — npx handles everything automatically:
macOS / Linux:
{
"mcpServers": {
"oe-mcp": {
"command": "npx",
"args": ["@openenterprise/oe-mcp", "--stdio", "/path/to/oe-mcp.yaml"]
}
}
}Windows: use npx.cmd instead of npx:
{
"mcpServers": {
"oe-mcp": {
"command": "npx.cmd",
"args": ["@openenterprise/oe-mcp", "--stdio", "C:\\path\\to\\oe-mcp.yaml"]
}
}
}Add this to ~/.mcp.json (Claude Code) and reload VS Code. Done.
Download (Standalone Binary)
Prefer a standalone binary? Download for your platform:
Platform | Binary |
Windows | |
Linux | |
macOS | |
Sample configs | oe-mcp-samples.zip — ready-to-use |
Quick Start (Binary)
1. Download the binary for your OS
# Linux / macOS — make executable
chmod +x oe-mcp-linux2. Create your config file (oe-mcp.yaml)
connectors:
- name: my-postgres
type: postgresql
host: localhost
port: 5432
database: mydb
user: postgres
password: secret
- name: my-codebase
type: filesystem
basePath: /home/user/projects/myapp
memory:
- key: project_context
value: "This is our main application database."3. Connect your AI app — see sections below for Claude Code, Cursor, and Windsurf.
Claude Code (VS Code Extension)
Option A — via npm (recommended, no binary download needed):
macOS / Linux:
{
"mcpServers": {
"oe-mcp": {
"command": "npx",
"args": ["@openenterprise/oe-mcp", "--stdio", "/path/to/oe-mcp.yaml"]
}
}
}Windows:
{
"mcpServers": {
"oe-mcp": {
"command": "npx.cmd",
"args": ["@openenterprise/oe-mcp", "--stdio", "C:\\path\\to\\oe-mcp.yaml"]
}
}
}Option B — via downloaded binary:
{
"mcpServers": {
"oe-mcp": {
"type": "stdio",
"command": "/path/to/oe-mcp-win.exe",
"args": ["--stdio", "/path/to/oe-mcp.yaml"]
}
}
}Reload VS Code — the MCP tools appear automatically in Claude Code.
Cursor / Windsurf / Claude Desktop (HTTP mode)
Start the server manually, then point your AI app at the URL.
# Start the MCP server
oe-mcp-win.exe --serve --port 4040 oe-mcp.yaml
# OE MCP Server listening on http://localhost:4040/mcpIn Cursor settings → MCP → Add server:
http://localhost:4040/mcpIn Claude Desktop claude_desktop_config.json:
{
"mcpServers": {
"oe-mcp": {
"url": "http://localhost:4040/mcp"
}
}
}Cloud Deployment (MCP as a Service)
Deploy oe-mcp-linux to any cloud server — AWS EC2, fly.io, Railway, DigitalOcean — and multiple developers connect to it via URL. No binary needed on each developer machine.
# On your cloud server
./oe-mcp-linux --serve --port 4040 /etc/oe-mcp/oe-mcp.yamlEach developer adds to their Cursor / Windsurf:
http://your-server.com:4040/mcpConfig File Reference (oe-mcp.yaml)
connectors:
- name: <display-name> # must be unique; shown as the tool prefix
type: <connection-type> # see Connector Catalog below
# ... connector-specific credentials
memory:
- key: <key>
value: <value> # seed defaults; overridden at runtime via memory_setExample — Multiple Connectors
connectors:
# ── SQL Databases ──────────────────────────────────────
- name: my-postgres
type: postgresql
host: db.company.com
port: 5432
database: production
user: readonly
password: secret
- name: my-mysql
type: mysql
host: localhost
port: 3306
database: mydb
user: root
password: secret
# ── NoSQL ──────────────────────────────────────────────
- name: my-mongo
type: mongodb
uri: mongodb://localhost:27017
database: mydb
- name: my-redis
type: redis
host: localhost
port: 6379
- name: my-elastic
type: elasticsearch
node: https://localhost:9200
apiKey: xxxxxxxxxxxx
# ── Object Storage ─────────────────────────────────────
- name: my-s3
type: s3
accessKeyId: AKIAXXXXXXXX
secretAccessKey: xxxxxxxxxxxx
region: us-east-1
bucket: my-bucket
# ── Cloud Drives ───────────────────────────────────────
- name: my-gdrive
type: gdrive
clientId: xxxx.apps.googleusercontent.com
clientSecret: xxxx
refreshToken: xxxx
# ── Code & Issue Tracking ──────────────────────────────
- name: my-github
type: github
token: ghp_xxxxxxxxxxxx
- name: my-jira
type: jira
host: https://company.atlassian.net
email: you@company.com
apiToken: xxxx
# ── Team Messaging ─────────────────────────────────────
- name: my-slack
type: slack
botToken: xoxb-xxxxxxxxxxxx
# ── Email ──────────────────────────────────────────────
- name: my-gmail
type: gmail
clientId: xxxx.apps.googleusercontent.com
clientSecret: xxxx
refreshToken: xxxx
- name: my-smtp
type: smtp
host: smtp.company.com
port: 587
user: you@company.com
password: secret
# ── SSH / Remote Server ────────────────────────────────
- name: my-server
type: ssh
host: server.company.com
port: 22
username: ubuntu
privateKey: /path/to/key.pem
# ── Filesystem ─────────────────────────────────────────
- name: my-codebase
type: filesystem
basePath: /home/user/projects
# ── REST API ───────────────────────────────────────────
- name: my-api
type: rest-api
baseUrl: https://api.company.com
headers:
Authorization: Bearer xxxx
# ── CRM ────────────────────────────────────────────────
- name: my-hubspot
type: hubspot
accessToken: pat-xxxxxxxxxxxx
# ── Message Queues ─────────────────────────────────────
- name: my-kafka
type: kafka
brokers:
- localhost:9092
memory:
- key: team
value: "Platform Engineering"
- key: environment
value: "production"Built-in Tools
Connector Tools
Each connector exposes a set of tools prefixed with the connector name. Examples:
Connector | Tools |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Memory Tools
Built-in memory tools available in every session:
Tool | Description |
| Store a key-value pair that persists across sessions |
| Retrieve a stored value by key |
| List all stored key-value pairs |
| Remove a stored key |
Memory is stored in oe-mcp-memory.json next to your oe-mcp.yaml and survives restarts.
Example usage in Claude Code:
"Remember that our main database is on prod-db.company.com" → Claude calls
memory_setwith keymain_db_hostand valueprod-db.company.com
Connector Catalog
2,600+ connectors across 45+ categories:
Category | Examples |
SQL Databases | PostgreSQL, MySQL, MSSQL, Oracle, SQLite, Snowflake, BigQuery, Redshift |
NoSQL / Cache | MongoDB, Redis, Elasticsearch, DynamoDB, Cassandra |
Object Storage | AWS S3, GCS, Azure Blob, MinIO, Cloudflare R2 |
Cloud Drives | Google Drive, OneDrive, Dropbox, Box |
Filesystem | Local directories — list, read, write, search |
Gmail, Outlook, Zoho Mail, SMTP | |
Team Messaging | Slack, Microsoft Teams, Discord, Telegram |
CRM / Productivity | HubSpot, Salesforce, Notion, Airtable |
Issue Tracking | GitHub, Jira, GitLab, Linear |
REST API | Any HTTP/REST endpoint |
GraphQL | Any GraphQL endpoint |
SSH / SFTP | Remote command execution, file transfer |
Message Queues | Kafka, AWS SQS, Google Pub/Sub, RabbitMQ |
Search | Perplexity, Google Search, Bing |
LDAP / Directory | Active Directory, OpenLDAP |
OCR / Vision | Azure Vision, Google Vision, AWS Textract |
Image Generation | OpenAI, FLUX, Stable Diffusion |
Speech & Audio | ElevenLabs, OpenAI TTS, Azure Speech |
Web3 / Blockchain | Ethereum, Polygon, Solana |
Helpdesk | Zendesk, Freshdesk, ServiceNow |
+ more | Healthcare (FHIR), ERP (SAP), Marketing, Analytics, ... |
Binary vs Node.js mode
The standalone binary works for all connector categories except Oracle, MSSQL, SQLite, and Snowflake — these use native C++ addons that cannot be bundled into a single executable.
If you need any of these four, run with Node.js instead:
git clone https://github.com/openenterprise-info/open-enterprise-ai-mcp-server.git cd open-enterprise-ai-mcp-server/server yarn install # stdio mode (Claude Code) node mcp/index.js --stdio /path/to/oe-mcp.yaml # serve mode (Cursor, Windsurf, cloud) node mcp/index.js --serve --port 4040 /path/to/oe-mcp.yamlAll other connectors (PostgreSQL, MySQL, MongoDB, Redis, S3, Slack, GitHub, REST API, SSH, filesystem, etc.) work directly with the binary — no Node.js required.
Sample Configs
Download oe-mcp-samples.zip for ready-to-use configs:
postgres · mysql · mongodb · github · slack · gdrive · ssh · filesystem · oracle · multi-connector
Each sample includes the complete oe-mcp.yaml with setup instructions in comments.
Transport Modes
Mode | Flag | Best for |
stdio |
| Claude Code VS Code extension, Claude Desktop — binary launched as child process automatically |
HTTP |
| Cursor, Windsurf, cloud deployments, multiple developers sharing one server |
Both modes are supported in the same binary — just pass the appropriate flag.
Part of Open Enterprise
OE MCP Server is part of the Open Enterprise platform.
⚡ Agent Runtime | open-enterprise-ai-agent-runtime — run YAML agents as CLI or HTTP server |
🖥️ Platform (Docker) | open-enterprise-ai-platform — full web app with workspaces, RAG, Agent Builder, DLP |
🌐 Website |
License
Apache-2.0 — free to use, modify, and deploy for any purpose, including commercial use. No usage limits. No telemetry. No call-home.
⭐ Star this repo · 🌐 Website · ⚡ Agent Runtime
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityFmaintenanceSecurely connects AI agents to multiple databases simultaneously while enabling collaborative learning from team query patterns, all while keeping data private by running locally.Last updated25874MIT
- AlicenseCqualityAmaintenanceProvides AI assistants with persistent memory and code intelligence across all tools and conversations. Features semantic search, knowledge graphs, decision tracking, and impact analysis with 60+ tools for universal context preservation.Last updated3632338MIT
- Alicense-qualityCmaintenanceConnect AI assistants to live Meta Ads, GA4, and Google Search Console data. 100% local, credentials machine-locked and encrypted. Supports Claude Desktop, Cursor, Windsurf, Cline, and more.Last updated1MIT
- Alicense-qualityCmaintenanceA production-grade platform that connects AI assistants to internal databases and filesystems through a single authenticated endpoint. It features role-based access control, SSO integration, and built-in tools for querying SQL databases and managing files with full audit logging.Last updated6MIT
Related MCP Connectors
Connect your team's living knowledge base — docs, data, issues, CRM — to Claude and ChatGPT.
Your company's brain for AI agents. Cited, permission-aware knowledge across every system.
Universal memory for AI agents and tools. Save, organize and search context anywhere.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/openenterprise-info/open-enterprise-ai-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server