🎩 You're Invited:Meet the Socket team at Black Hat in Las Vegas, August 3-6.RSVP
Sign In

@openenthrium/oe-mcp

Package Overview
Dependencies
Maintainers
1
Versions
12
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@openenthrium/oe-mcp

OE MCP Server - connect Claude Code, Cursor & Windsurf to enterprise data sources. One binary, one JSON config.

latest
Source
npmnpm
Version
1.6.7
Version published
Weekly downloads
875
Maintainers
1
Weekly downloads
 
Created
Source

OE MCP Server · @openenthrium/oe-mcp

Connect Claude Code, Cursor, Windsurf, Codex, Claude Desktop, and VS Code to enterprise data sources — databases, APIs, files, SSH, messaging, and more. One binary. One JSON config.

npm License: Apache 2.0 Website Discord

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, Codex, Claude Desktop, or VS Code 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 JSON file.
  • 45+ connector categories. Enterprise systems supported out of the box.
  • Two transport modes. --stdio for Claude Code, Cursor, Windsurf, Codex, and Claude Desktop (launched as a child process); --serve for cloud deployments or sharing one server across a team.
  • Persistent memory. Built-in memory_set / memory_get / memory_list / memory_delete tools — context survives across sessions.
  • Self-hosted. Runs on your own machine. No cloud dependency. Own your data.

Quick Start

1. Create your config file (oe-mcp.json)

{
  "connectors": [
    { "name": "my-postgres", "type": "postgresql",    "host": "localhost", "port": 5432, "database": "mydb", "user": "postgres", "password": "secret" },
    { "name": "my-mysql",    "type": "mysql",         "host": "localhost", "port": 3306, "database": "mydb", "user": "root",     "password": "secret" },
    { "name": "my-mongo",    "type": "mongodb",       "uri": "mongodb://localhost:27017", "database": "mydb" },
    { "name": "my-redis",    "type": "redis",         "host": "localhost", "port": 6379 },
    { "name": "my-s3",       "type": "s3",            "accessKeyId": "AKIAXXXXXXXX", "secretAccessKey": "xxxxxxxxxxxx", "region": "us-east-1", "bucket": "my-bucket" },
    { "name": "my-gdrive",   "type": "gdrive",        "clientId": "xxxx.apps.googleusercontent.com", "clientSecret": "xxxx", "refreshToken": "xxxx" },
    { "name": "my-github",   "type": "github",        "repoUrl": "https://github.com/your-org/your-repo", "personalAccessToken": "ghp_xxxxxxxxxxxx" },
    { "name": "my-slack",    "type": "slack",         "botToken": "xoxb-xxxxxxxxxxxx" },
    { "name": "my-gmail",    "type": "gmail",         "clientId": "xxxx.apps.googleusercontent.com", "clientSecret": "xxxx", "refreshToken": "xxxx" },
    { "name": "my-email",    "type": "smtp",          "host": "smtp.company.com", "port": 587, "user": "you@company.com", "password": "secret" },
    { "name": "my-server",   "type": "ssh",           "host": "server.company.com", "port": 22, "username": "ubuntu", "privateKey": "-----BEGIN OPENSSH PRIVATE KEY-----\nYOUR_PRIVATE_KEY_CONTENT\n-----END OPENSSH PRIVATE KEY-----" },
    { "name": "my-codebase", "type": "filesystem",   "basePath": "/home/user/projects/myapp" },
    { "name": "my-api",      "type": "rest-api",      "baseUrl": "https://api.company.com", "headers": { "Authorization": "Bearer xxxx" } },
    { "name": "my-jira",     "type": "jira",          "host": "https://company.atlassian.net", "email": "you@company.com", "apiToken": "xxxx" },
    { "name": "my-hubspot",  "type": "hubspot",       "accessToken": "pat-xxxxxxxxxxxx" },
    { "name": "my-kafka",    "type": "kafka",         "brokers": ["localhost:9092"] },
    { "name": "my-elastic",  "type": "elasticsearch", "node": "https://localhost:9200", "apiKey": "xxxxxxxxxxxx" }
  ],
  "memory": [
    { "key": "team",        "value": "Platform Engineering" },
    { "key": "environment", "value": "production" }
  ]
}

2. Add to your AI app's MCP config (Claude Code, Cursor, Windsurf, Codex, Claude Desktop, VS Code)

macOS / Linux:

{
  "mcpServers": {
    "oe-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@openenthrium/oe-mcp", "--stdio", "/path/to/oe-mcp.json"]
    }
  }
}

Windows:

{
  "mcpServers": {
    "oe-mcp": {
      "type": "stdio",
      "command": "npx.cmd",
      "args": ["-y", "@openenthrium/oe-mcp", "--stdio", "C:\\path\\to\\oe-mcp.json"]
    }
  }
}

Note: -y skips npx's install confirmation prompt — without it, npx blocks waiting for keyboard input and the MCP connection never opens.

3. Reload your AI app — your connectors appear as tools automatically.

Test Your Connection and Memory

Test Connectors

Once connected, ask Claude in plain language:

"What connectors do you have access to?"

Claude will list every connected tool with its available actions. Example response:

ConnectorTools
my-postgresquery
my-githublist_files, read_file, create_issue, get_issue, search_issues
my-slacklist_channels, post_message, search_messages
my-codebaselist_dir, read_file, write_file, search_files

You can also run /mcp in Claude Code to see the server status and total tool count.

Test Memory

OE MCP has built-in persistent memory that survives restarts. Use plain language or direct tool calls:

Save a memory:

"Remember that our production database host is prod-db.company.com"

Claude calls memory_set with key = main_db_host, value = prod-db.company.com.

Retrieve a memory:

"What is our production database host?"

Claude calls memory_get with key = main_db_host and returns the stored value.

List all memories:

"What do you remember about our project?"

Claude calls memory_list and returns all stored key-value pairs.

Delete a memory:

"Forget the production database host."

Claude calls memory_delete with key = main_db_host to remove it.

Memory is stored in oe-mcp-memory.json next to your oe-mcp.json and persists across sessions and restarts.

Run YAML Agents (run_agent)

OE MCP can run OE Runtime YAML agents directly from Claude Code, Cursor, Windsurf, Codex, or any MCP-compatible AI app — no terminal required.

Just ask Claude:

"Run my database analyst agent at /home/user/agents/db-analyst/agent.yaml"

Claude calls run_agent, which executes:

npx -y @openenthrium/oe-runtime agent.yaml --config oe-config.json

And returns the full agent output back to your AI app.

Parameters:

ParameterTypeRequiredDescription
filestringAbsolute path to the agent.yaml file
paramsobjectKey-value pairs passed to the agent as --param key=value flags

Config auto-detection: OE MCP looks for oe-config.json in the same directory as agent.yaml. If found, it uses that config. Otherwise it falls back to the oe-mcp.json config.

Requires OE Runtime. The agent directory must have a valid oe-config.json with llm and connectors configured. See OE Runtime for agent authoring docs.

Supported Connectors

Connectors across 45+ categories:

CategoryExamples
SQL DatabasesPostgreSQL, MySQL, MSSQL, Oracle, SQLite, Snowflake, BigQuery, Redshift
NoSQL / CacheMongoDB, Redis, Elasticsearch, DynamoDB, Cassandra
Object StorageAWS S3, GCS, Azure Blob, MinIO, Cloudflare R2
Cloud DrivesGoogle Drive, OneDrive, Dropbox, Box
FilesystemLocal directories — list, read, write, search
EmailGmail, Outlook, Zoho Mail, SMTP
Team MessagingSlack, Microsoft Teams, Discord, Telegram
CRMHubSpot, Salesforce, Notion, Airtable
Issue TrackingGitHub, Jira, GitLab, Linear
REST APIAny HTTP/REST endpoint
SSH / SFTPRemote command execution, file transfer
Message QueuesKafka, AWS SQS, Google Pub/Sub, RabbitMQ
+ moreLDAP, OCR, Image Generation, Healthcare, ERP, Web3, ...

Transport Modes

ModeFlagBest for
stdio--stdioClaude Code, Cursor, Windsurf, Codex, Claude Desktop — binary launched as child process by the AI app
HTTP--serve --port 4040Cloud deployments, multiple developers sharing one server

Built-in Memory

Every session includes persistent memory tools:

ToolDescription
memory_setStore a key-value pair across sessions
memory_getRetrieve a stored value
memory_listList all stored pairs
memory_deleteRemove a stored key

Memory is stored in oe-mcp-memory.json next to your oe-mcp.json and survives restarts.

Built-in Action Log

Every connector tool call is automatically logged to oe-mcp-log.json:

ToolDescription
log_listList recent connector action log entries (newest first, supports limit param)
log_clearClear all entries from the action log

Example log entry:

{
  "ts": "2026-08-08T04:59:33.289Z",
  "connector": "my-postgres",
  "tool": "query",
  "input": { "sql": "SELECT * FROM users LIMIT 10" },
  "result": "ok"
}

License

Apache-2.0 — free to use, modify, and deploy for any purpose including commercial use.

Keywords

mcp

FAQs

Package last updated on 09 Aug 2026

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts