Stripe MCP
MCP server integrating with Stripe - tools for customers, products, payments, and more.
MCP server for Amazon S3 and S3-compatible endpoints (LocalStack, MinIO). Single Go binary.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 7/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 7/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
通过 3/3 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
用 S3 MCP Connector 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 S3 MCP Connector,或回答中出现 S3 MCP Connector 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 S3 MCP Connector
S3 MCP Connector 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 S3 MCP Connector 的应用
B · 网店与支付 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
Claude Code 暂时无法连接 S3 MCP Connector
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 S3 MCP Connector 的应用
Cursor 暂时无法连接 S3 MCP Connector
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 S3 MCP Connector 的应用
VS Code 暂时无法连接 S3 MCP Connector
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 S3 MCP Connector 的应用
AWS_ACCESS_KEY_ID 机密 必填 envAWS_SECRET_ACCESS_KEY 机密 必填 envAWS_REGION envS3_ENDPOINT_URL envS3_FORCE_PATH_STYLE env说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月18日
注册名称已通过 GitHub 账户 FerhatDundar 验证,该账户拥有此仓库
代码最后更新于2个月前
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/ferhatdundar-s3-mcp-connector)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于2个月前,最新版本(0.2.0)于5个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 MCPB。
同一分类中有:Stripe MCP, flightclaw, Trade It, Marketplace Ad Pros: Amazon Ads & Seller Central, idealo MCP Server
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP server integrating with Stripe - tools for customers, products, payments, and more.
Search ~300 airlines and book flights with a checkout link. OAuth sign-in by email code.
Connect brokerage accounts to AI assistants: holdings, orders, asset lookup, and approved trading.
Amazon Ads, Seller Central, Vendor Central and AMC data for AI agents. Read-only by default.
Search products, compare prices and discover deals across 6 European markets with your AI assistant.
| 本项 S3 MCP Connector | Stripe MCP | flightclaw | Trade It | Marketplace Ad Pros: Amazon Ads & Seller Central | idealo MCP Server | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 是 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 是 | 否 | 否 | 否 | 否 |
| 基础检查 | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | MIT | MIT | MIT | CC0-1.0 | MIT | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Talk to Amazon S3 — or LocalStack, MinIO, any S3-compatible store — from an MCP-speaking agent.
A single static Go binary that speaks the Model Context Protocol and exposes 8 tools for working with S3: list buckets, list/read/write/delete objects, create/delete buckets. Point it at real AWS or at a local LocalStack/MinIO instance with one environment variable — same binary, same tools, zero code changes.
No Python, no uv, no runtime dependency to install — just a binary and an .mcp.json.
An agent that can only *talk about* your S3 buckets isn't that useful.
This gives it hands: it can look inside a bucket, read a config file out
of it, drop a report back in, or clean up a stale prefix — safely, with
guardrails on size and destructive actions built in.
| Tool | What it does | Write? |
|---|---|---|
s3_list_buckets | List buckets visible to the credentials | |
s3_list_objects | List objects in a bucket, optional prefix, paginated | |
s3_head_object | Object metadata (size, type, ETag) without downloading | |
s3_get_object | Read an object's content — text or base64, size-capped | |
s3_put_object | Write a small text/base64 object (≤ 5 MB) | ✍️ |
s3_delete_object | Delete one object | 🗑️ destructive |
s3_create_bucket | Create a bucket | ✍️ |
s3_delete_bucket | Delete an *empty* bucket | 🗑️ destructive |
Every tool accepts an optional response_format: markdown (default, pretty tables for a chat UI) or json (for programmatic use).
s3_get_object auto-detects text vs. binary content and caps output at 200,000 bytes by default (raise via max_bytes, hard cap 5,000,000) — it's built for reading configs, logs, and small data files, not bulk transfer. Reach for the AWS CLI or SDK directly for large objects.
Fastest path: grab a prebuilt bundle from the latest release — download s3-mcp-connector-plugin- - - .zip, unzip it, and point Cowork/Claude at the plugin/ folder inside (see step 4 of SETUP.md). No Go toolchain required.
From source:
# 1. Build
cd go-server go mod tidy go build -o s3-connector-server . cp s3-connector-server ../plugin/servers/go/
cd .. docker compose up -d
export AWS_ACCESS_KEY_ID=test export AWS_SECRET_ACCESS_KEY=test export AWS_REGION=us-east-1 export S3_ENDPOINT_URL=http://localhost:4566 export S3_FORCE_PATH_STYLE=true
./go-server/s3-connector-server # serves MCP over stdio
Or make build && make localstack-up — see the Makefile for every shortcut (test, vet, fmt, lint, tidy, localstack-down).
Full walkthrough — including wiring this up as a Claude/Cowork plugin and switching from LocalStack to real AWS — is in [SETUP.md](SETUP.md).
Everything is environment variables, passed through by the plugin's .mcp.json:
| Variable | Purpose | Default |
|---|---|---|
AWS_ACCESS_KEY_ID / AWS_SECRET_ACCESS_KEY | AWS credentials. Any non-empty values work against LocalStack. | — |
AWS_REGION | Region to use. | us-east-1 |
S3_ENDPOINT_URL | Custom endpoint. Leave unset for real AWS. | *(unset)* |
S3_FORCE_PATH_STYLE | true for LocalStack/MinIO (path-style addressing). | false |
This isn't a toy script — it's got the same checks you'd expect from a production Go service:
go test ./...)All of it runs in CI on every push and PR.
Versions follow semver and are cut automatically by release-please from Conventional Commits on main:
fix: ... → patch (v0.1.0 → v0.1.1)feat: ... → minor (v0.1.1 → v0.2.0)feat!: ... / BREAKING CHANGE: footer → major (v0.2.0 → v1.0.0)Every merged PR updates a standing "chore(main): release vX.Y.Z" PR with an auto-generated CHANGELOG.md. Merging that PR:
server.json from those exact assets (fresh version + SHA-256 hashes) and publishes it to the official MCP Registry via mcp-publisher, authenticated with GitHub OIDC — no stored secretsSee .github/workflows/release-please.yml and .github/workflows/publish-mcp-registry.yml (also runnable by hand for an existing tag via workflow_dispatch).
s3-mcp-connector/
├── README.md ← you are here ├── SETUP.md ← step-by-step setup guide (LocalStack + real AWS) ├── CONTRIBUTING.md ← how to contribute ├── CODE_OF_CONDUCT.md ├── SECURITY.md ← vulnerability reporting ├── CODEOWNERS ├── LICENSE ← MIT ├── Makefile ← build / test / lint / localstack shortcuts ├── docker-compose.yml ← LocalStack, for local testing ├── .golangci.yml ← lint rules ├── release-please-config.json ← semver/changelog automation config ├── .release-please-manifest.json ├── server.json ← MCP Registry manifest (regenerated fresh per release by CI) ├── scripts/ │ └── render-server-json.sh ← rebuilds server.json from a release's zip assets ├── .github/ │ ├── workflows/ │ │ ├── ci.yml ← build, vet, test, lint, govulncheck │ │ ├── codeql.yml ← security scanning │ │ ├── pr-title.yml ← Conventional Commits PR title check │ │ ├── release-please.yml ← version PRs, tagging, GitHub releases │ │ ├── publish-mcp-registry.yml ← publishes server.json to the MCP Registry │ │ └── rebuild-release-assets.yml ← manual re-attach fallback │ ├── ISSUE_TEMPLATE/ │ ├── PULL_REQUEST_TEMPLATE.md │ └── dependabot.yml ├── go-server/ ← the MCP server source │ ├── main.go │ ├── main_test.go │ ├── go.mod / go.sum │ └── README.md └── plugin/ ← installable Cowork/Claude plugin ├── .claude-plugin/plugin.json ├── .mcp.json ← holds credentials locally — never commit real ones └── servers/go/ ← compiled binary goes here
PRs and issues are very welcome — see [CONTRIBUTING.md](CONTRIBUTING.md) for the full guide (setup, coding conventions, how to add a new tool) and the [Code of Conduct](CODE_OF_CONDUCT.md).
main is protected: every change, including the maintainer's, lands via pull request with CI green. PR titles must follow Conventional Commits — that's what drives the automatic versioning above.
Found a security issue? Please follow [SECURITY.md](SECURITY.md) instead of opening a public issue.
MIT © Ferhat Dundar