Quotes By Api Ninjas MCP Server
Provides access to the Quotes By Api Ninjas API for retrieving random quotes by category, distributed as a Python package on PyPI.
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., "@Quotes By Api Ninjas MCP Servergive me an inspirational quote about leadership"
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.
Quotes By Api Ninjas MCP Server
用于访问 Quotes By Api Ninjas API 的 MCP 服务器。
🚀 使用 EMCP 平台快速体验
EMCP 是一个强大的 MCP 服务器管理平台,让您无需手动配置即可快速使用各种 MCP 服务器!
快速开始:
🌐 访问 EMCP 平台
📝 注册并登录账号
🎯 进入 MCP 广场,浏览所有可用的 MCP 服务器
🔍 搜索或找到本服务器(
bach-quotes_by_api_ninjas)🎉 点击 "安装 MCP" 按钮
✅ 完成!即可在您的应用中使用
EMCP 平台优势:
✨ 零配置:无需手动编辑配置文件
🎨 可视化管理:图形界面轻松管理所有 MCP 服务器
🔐 安全可靠:统一管理 API 密钥和认证信息
🚀 一键安装:MCP 广场提供丰富的服务器选择
📊 使用统计:实时查看服务调用情况
立即访问 EMCP 平台 开始您的 MCP 之旅!
Related MCP server: Random Word By Api Ninjas
简介
这是一个 MCP 服务器,用于访问 Quotes By Api Ninjas API。
PyPI 包名:
bach-quotes_by_api_ninjas版本: 1.0.0
传输协议: stdio
安装
从 PyPI 安装:
pip install bach-quotes_by_api_ninjas从源码安装:
pip install -e .运行
方式 1: 使用 uvx(推荐,无需安装)
# 运行(uvx 会自动安装并运行)
uvx --from bach-quotes_by_api_ninjas bach_quotes_by_api_ninjas
# 或指定版本
uvx --from bach-quotes_by_api_ninjas@latest bach_quotes_by_api_ninjas方式 2: 直接运行(开发模式)
python server.py方式 3: 安装后作为命令运行
# 安装
pip install bach-quotes_by_api_ninjas
# 运行(命令名使用下划线)
bach_quotes_by_api_ninjas配置
API 认证
此 API 需要认证。请设置环境变量:
export API_KEY="your_api_key_here"环境变量
变量名 | 说明 | 必需 |
| API 密钥 | 是 |
| 不适用 | 否 |
| 不适用 | 否 |
在 Cursor 中使用
编辑 Cursor MCP 配置文件 ~/.cursor/mcp.json:
{
"mcpServers": {
"bach-quotes_by_api_ninjas": {
"command": "uvx",
"args": ["--from", "bach-quotes_by_api_ninjas", "bach_quotes_by_api_ninjas"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}在 Claude Desktop 中使用
编辑 Claude Desktop 配置文件 claude_desktop_config.json:
{
"mcpServers": {
"bach-quotes_by_api_ninjas": {
"command": "uvx",
"args": ["--from", "bach-quotes_by_api_ninjas", "bach_quotes_by_api_ninjas"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}可用工具
此服务器提供以下工具:
v1quotes
Returns one (or more) random quotes.
端点: GET /v1/quotes
参数:
category(string): category to limit results to. Possible values are: age alone amazing anger architecture art attitude beauty best birthday business car change communications computers cool courage dad dating death design dreams education environmental equality experience failure faith family famous fear fitness food forgiveness freedom friendship funny future god good government graduation great happiness health history home hope humor imagination inspirational intelligence jealousy knowledge leadership learninglimit(number): How many results to return. Must be between 1 and 10. Default is 1.
技术栈
传输协议: stdio
HTTP 客户端: httpx
许可证
MIT License - 详见 LICENSE 文件。
开发
此服务器由 API-to-MCP 工具生成。
版本: 1.0.0
Available Tools
1 toolv1quotesB
Returns one (or more) random quotes.
| Name | Required | Description | Default |
|---|---|---|---|
| category | No | category to limit results to. Possible values are: age alone amazing anger architecture art attitude beauty best birthday business car change communications computers cool courage dad dating death design dreams education environmental equality experience failure faith family famous fear fitness food forgiveness freedom friendship funny future god good government graduation great happiness health history home hope humor imagination inspirational intelligence jealousy knowledge leadership learning | |
| limit | No | How many results to return. Must be between 1 and 10. Default is 1. | 0 |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It mentions 'random quotes' but doesn't disclose behavioral traits like source of quotes, rate limits, authentication needs, or what 'random' entails (e.g., uniform distribution, seed). This leaves significant gaps for a tool with potential variability.
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?
The description is a single, efficient sentence with zero waste. It is appropriately sized and front-loaded, clearly stating the core functionality without unnecessary elaboration.
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?
Given the tool's low complexity (2 optional parameters, no output schema, no annotations), the description is minimally adequate. However, it lacks details on output format (e.g., structure of returned quotes) and behavioral context, which would be helpful despite the simple schema.
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?
Schema description coverage is 100%, so the schema fully documents both parameters. The description adds no parameter-specific information beyond implying quantity via 'one or more,' which loosely relates to the 'limit' parameter. This meets the baseline for high schema coverage.
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?
The description clearly states the tool's purpose with a specific verb ('Returns') and resource ('random quotes'), and specifies quantity ('one or more'). However, it doesn't distinguish from siblings since none exist, so it cannot achieve a perfect 5.
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?
The description provides no guidance on when to use this tool versus alternatives, prerequisites, or constraints beyond what's implied by the parameters. With no sibling tools, this is less critical, but still lacks explicit usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
v1.0.0- First observed
v1quotes
TDQS
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as returning random quotes, leaving no room for misselection.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'v1quotes' follows a single pattern without any deviation or mixing of conventions.
A single tool for a quotes server feels thin and under-scoped. While it provides a basic random quote function, it lacks operations like searching by author, category, or keyword, which are typical for quote services. This minimal set may limit agent capabilities.
The tool surface is severely incomplete for a quotes domain. It only offers random quotes, missing essential operations such as filtering by author, topic, or date, retrieving specific quotes, or managing a collection. This creates significant gaps that could lead to agent failures in broader tasks.
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 Connectors
20+ pay-per-use APIs: image gen, crypto data, email verify, SSL check, web scraping, and more.
Discover and call pay-per-request (x402) APIs, ranked by reliability, latency and price.
17-model LLM gateway + 350+ data/KYB/sanctions tools. Pay-per-call USDC via x402, no API key.
Live & historical FX rates and currency conversion for AI agents. No API keys.
Related MCP Servers
- FlicenseNot gradedqualityNot gradedmaintenanceProvides access to inspirational quotes through a free API, enabling users to retrieve random quotes, search quotes by keywords, and fetch specific quotes by ID.-
- AlicenseBqualityDmaintenanceProvides access to API Ninjas Random Word API to generate random words by type (noun, verb, adjective, adverb) for creative writing, games, and language learning applications.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Zenquotes's tools and services through a unified API, allowing users to access quotes and related functionality via natural language.MIT
- FlicenseAqualityBmaintenanceEnables users to list quote categories and retrieve random quotes from a local JSON file via MCP tools, with no API key required.2-
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/BACH-AI-Tools/quotes_by_api_ninjas'
If you have feedback or need assistance with the MCP directory API, please join our Discord server