MCP Integration Server

MCP数据服务

提供方 henrymclane09

数据服务 HTTP · 远程 混合方式 社区 / 第三方

Enables agents to interact with Salesforce, Atlassian (Jira/Confluence), and Supabase through standardized tools and resources. Provides both read-only access for querying data and write operations for managing records across these enterprise platforms.

一句话选型结论

按资料字段整理

MCP Integration Server 属于数据服务类 MCP 服务器,HTTP · 远程,混合方式,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类数据服务 传输方式HTTP · 远程 鉴权混合方式 部署方式支持远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

数据服务
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

安装与配置

HTTP · 远程 混合方式
连远程 HTTPS 端点,通常为 Streamable HTTP
  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
数据库查询

用自然语言查库、取数,不用手写 SQL。

数据同步与清洗

把多来源数据拉到一处做整理。

报表取数

按口径快速拉出统计结果。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 基础信息齐全,可以先按官方文档接入试跑。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好混合方式对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在数据服务场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
MCP Integration Server当前 未标注 HTTP · 远程 支持远程部署 无 2026-05-17
Memory 9d25f64e 9 未标注 未标注 无 2026-05-17
Getzep MCP 9 stdio · 本地进程 本地部署 有 2026-05-17
anything-llm 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Prisma MCP Server 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Astr Bot 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

数据服务
字段来自项目仓库与公开索引,中文说明由本站标注
提供方henrymclane09上游标注的维护方 henrymclane09
分类数据服务本站按上游分类展示
连接方式HTTP · 远程连远程 HTTPS 端点,通常为 Streamable HTTP
鉴权方式混合方式远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型支持远程部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

7.3 KB
来自项目仓库与上游目录的原文,未做删改

MCP Integration Server (Salesforce • Atlassian • Supabase)

A TypeScript Model Context Protocol (MCP) server that exposes your Salesforce, Atlassian (Jira/Confluence), and internal resources as tools and resources agents can call in a standardized way.

This README covers:

What the server does
How to configure credentials
How to build and run locally
How to smoke-test tools without any desktop client
Operational/safety notes

At a glance

Language/Runtime: TypeScript on Node 18+ (Node 20+ recommended)
MCP Transport: stdio (the MCP server is launched by the client and communicates over standard I/O)
Key integrations: Salesforce REST, Jira/Confluence REST, Supabase (logging + example resources)
Hardening included: central HTTP client with timeouts, basic log redaction, environment isolation

Repo layout

Repo layout```text

MCPtest-main/
├─ mcp-server/
│ ├─ index.ts # MCP server (stdio) wiring handlers for tools/resources
│ ├─ types.ts # Tool/Resource typing helpers
│ ├─ runtime/
│ │ ├─ context.ts # Central env + Supabase client
│ │ └─ http.ts # Shared axios instance (timeouts, sane defaults)
│ ├─ tools/
│ │ ├─ salesforce.ts # salesforce_ tools (query/get/search + writes)
│ │ ├─ atlassian.ts # jira_
/ confluence_ tools
│ │ ├─ analytics.ts # example tools backed by Supabase
│ │ ├─ documents.ts # example doc tools backed by Supabase
│ │ └─ utilities.ts # calculate, format_date, generate_uuid, hash_string, http_request
│ ├─ resources/
│ │ ├─ salesforce.ts # salesforce://
read-only resources
│ │ ├─ atlassian.ts # jira:// / confluence:// resources
│ │ ├─ analytics.ts # analytics:// resources from Supabase
│ │ └─ documents.ts # document://
resources from Supabase
│ └─ tsconfig.json
├─ scripts/
│ ├─ mcp-smoketest.mjs # headless tool caller (launches server over stdio)
│ └─ list-tools.mjs # prints all tool names
├─ .env.example
├─ package.json
└─ README.md


Prerequisites
Node.js 18+ (20+ recommended)
An editor with TypeScript support
(Optional) Accounts/API tokens for Salesforce, Jira, Confluence, Supabase

Environment variables
Copy .env.example to .env in the project root and fill in what you need. Only the integrations you use must be set.

Supabase (used for logging + example resources)
Variable    Description
SUPABASE_URL    Your Supabase project URL
SUPABASE_ANON_KEY or SUPABASE_SERVICE_ROLE_KEY  Key to access your Supabase (start with ANON; use Service Role only with proper RLS)

Backward-compatible names VITE_SUPABASE_URL / VITE_SUPABASE_ANON_KEY are still read by runtime/context.ts, but prefer the SUPABASE_* names for clarity.

# Salesforce```
Variable    Description
SALESFORCE_INSTANCE_URL e.g., https://your-domain.my.salesforce.com
SALESFORCE_ACCESS_TOKEN OAuth/Bearer token with appropriate scopes
Jira (Atlassian)
Variable    Description
JIRA_URL    e.g., https://your-domain.atlassian.net
JIRA_EMAIL  Atlassian account email
JIRA_API_TOKEN  API token generated from Atlassian account
Confluence (Atlassian)
Variable    Description
CONFLUENCE_URL  e.g., https://your-domain.atlassian.net/wiki
CONFLUENCE_EMAIL    Atlassian account email
CONFLUENCE_API_TOKEN    API token generated from Atlassian account

Tip: Start with read-only tools (queries, searches) before enabling any write-paths.

Install, build, and run locally

From the project root:
Install deps
npm install

Build the MCP server
npm run build:mcp

This compiles TypeScript to mcp-server/dist/index.js.

Smoke-test a tool (no desktop client required)
The smoketest script launches the MCP server over stdio and calls a tool by name.

Show available tools (optional):
node scripts/list-tools.mjs

Call a safe tool first (from utilities.ts), e.g.:

mac/linux

node scripts/mcp-smoketest.mjs calculate '{"expression":"2+2*5"}'

windows powershell (escape quotes)

node scripts/mcp-smoketest.mjs calculate "{""expression"":""2+2*5""}"

Call an integration tool (only after your .env is set), for example:

Salesforce (read-only)

node scripts/mcp-smoketest.mjs salesforce_query '{"query":"SELECT Id, Name FROM Account LIMIT 1"}'

Jira (search)

node scripts/mcp-smoketest.mjs jira_search_issues '{"jql":"assignee = currentUser() ORDER BY created DESC"}'

What you should see: JSON output with a content array containing the tool’s result (in text-serialized JSON). If an auth error appears, recheck your .env.

How it works (short version)

mcp-server/index.ts stands up a JSON-RPC MCP Server over stdio with handlers for:

ListTools → discovers all tools (from tools/)

CallTool → routes tool calls to the correct handler

ListResources/ReadResource → exposes read-only document/analytics/salesforce/atlassian resources

mcp-server/runtime/context.ts centralizes:

Environment variable parsing

Supabase client creation

mcp-server/runtime/http.ts provides a shared axios instance with:

20s timeout

Controlled status handling

Tools log to Supabase’s api_logs (if configured). Arguments are passed through a small redaction helper to avoid storing secrets.

Configuration details

HTTP client: mcp-server/runtime/http.ts sets a 20s timeout and friendly status handling (validateStatus). If you need retries, add an axios interceptor there once.

Logging: Tool handlers call a logApiCall helper that inserts rows into api_logs. Sensitive fields like tokens are redacted before insert.

Responses: Tools consistently return { content: [{ type: "text", text: "" }] }. This keeps client parsing predictable across runtimes.

Safety notes

Start read-only. Begin with tools like salesforce_query or jira_search_issues. Enable writes (create/update/delete/transition) later.

Guard writes. A simple pattern is to require a confirm: "yes" or a dryRun: true default and only execute state-changing calls when explicitly requested. (Planned: dryRun fields on Salesforce/Atlassian write tools.)

Least privilege. Use the minimum API scopes necessary for each integration.

RLS on Supabase. If you use ANON keys, set Row Level Security so logs are not world-readable.

Troubleshooting

Cannot find module mcp-server/dist/index.js
You skipped the build step or ran from the wrong folder.
Fix: npm run build:mcp then ensure mcp-server/dist/index.js exists.

Hangs or very slow responses
External API may be slow. Timeouts are set to 20s; adjust in runtime/http.ts if needed.

Auth errors
Double-check your .env. Try a non-integrated tool (calculate) to confirm the server/client plumbing.

Tool not found
Run node scripts/list-tools.mjs to see the exact tool names, then pass one to the smoketest.

Extending

Add new integrations by creating a new file in mcp-server/tools/yourservice.ts and registering tools that return structured results.

Expose read-only views through mcp-server/resources/yourservice.ts with your own URI scheme (e.g., yourservice://…).

If you later use a GUI agent runtime or desktop client, point it at node mcp-server/dist/index.js as an MCP stdio server.

Scripts reference

package.json (root) includes:

build:mcp – compile the MCP server

mcp:server – run the compiled server directly (usually launched by a client)

(optional) tools – list tool names

(optional) smoke – shorthand to run the smoketestMCPtest

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
MCP Integration Server 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

MCP Integration Server 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

MCP Integration Server 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

MCP Integration Server 需要 API Key 吗?

资料标注需要混合方式认证,使用前准备好对应凭据,并按最小权限配置。

MCP Integration Server 能提供哪些能力?

资料显示能力标签包括 集成服务、资源管理、API集成、OAuth认证、HTTP。具体工具清单以官方文档为准。

MCP Integration Server 需要什么运行环境?

属于远程端点,不需要在本地装运行时。

MCP Integration Server 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为HTTP · 远程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。