Allows installation of the Fetch API MCP server through npm package management, making it accessible as a global command-line utility.
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., "@Fetch API MCP Server fetch https://api.github.com/repos/glama-ai/mcp with headers Authorization: Bearer token123"
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.
这是一个基于MCP（Model Context Protocol）的API请求服务器，可以发送各种HTTP请求并返回结果。
支持多种HTTP方法（GET, POST, PUT, DELETE等）
支持自定义请求头
支持表单数据提交
支持JSON数据提交
支持Cookie设置
自动处理不同类型的响应（JSON, 文本, 二进制）
Related MCP server: MCP Boilerplate
npm 安装
npm install -g fetch-api-mcp打开 cursor mcp 配置，添加配置项：
"fetch-api": {
"command": "mcp-server-fetch-api"
}npm installnpm start或者直接运行：
node src/index.jsMCP服务器接受以下参数：
url: 请求的URL（必填）
method: 请求方法，默认为GET
headers: 请求头，对象格式
formData: 表单数据，对象格式
jsonData: JSON数据，对象格式
cookies: Cookie数据，对象格式
服务器返回以下数据：
status: HTTP状态码
statusText: HTTP状态文本
headers: 响应头
data: 响应数据（会根据Content-Type自动解析为JSON、文本或Base64编码的二进制数据）
{
"url": "https://api.example.com/data",
"method": "GET",
"headers": {
"User-Agent": "MCP-Fetch-API/1.0"
}
}{
"url": "https://api.example.com/submit",
"method": "POST",
"headers": {
"User-Agent": "MCP-Fetch-API/1.0"
},
"jsonData": {
"name": "测试用户",
"email": "test@example.com"
}
}{
"url": "https://api.example.com/form",
"method": "POST",
"formData": {
"username": "testuser",
"password": "password123"
}
}{
"url": "https://api.example.com/profile",
"method": "GET",
"cookies": {
"session": "abc123",
"user_id": "12345"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | ||
| method | No | GET | |
| headers | No | ||
| formData | No | ||
| jsonData | No | ||
| cookies | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'request' stands alone with no other tools to confuse it with.
A single tool inherently has perfect naming consistency, as there are no other tool names to compare it against. The name 'request' is clear and follows no conflicting patterns.
A single tool for an API server is too few for the apparent scope, as typical API interactions require multiple operations like GET, POST, PUT, DELETE. This minimal set is insufficient for comprehensive coverage.
The tool surface is severely incomplete for an API server domain. With only a generic 'request' tool and no descriptions, it lacks specific operations (e.g., for different HTTP methods or endpoints), making it impossible to perform standard CRUD workflows.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
A Model Context Protocol server for Wix AI tools
Model Context Protocol server for Studex tools, notifications, and profile integrations
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/jethroHuang/fetch-api-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server