API MCP Server
# MCP Server for Calling Api MCP Server
A custom MCP server
This is a TypeScript-based MCP server that implements a simple notes system. It demonstrates core MCP concepts by providing:
- Resources representing text notes with URIs and metadata
- Tools for creating new notes
- Prompts for generating summaries of notes
## Features
### Resources
- List and access notes via `note://` URIs
- Each note has a title, content and metadata
- Plain text mime type for simple content access
### Tools
- `create_note` - Create new text notes
- Takes title and content as required parameters
- Stores note in server state
### Prompts
- `summarize_notes` - Generate a summary of all stored notes
- Includes all note contents as embedded resources
- Returns structured prompt for LLM summarization
## Development
Install dependencies:
```bash
npm install
```
Build the server:
```bash
npm run build
```
For development with auto-rebuild:
```bash
npm run watch
```
## Installation
To use with Claude Desktop, add the server config:
On MacOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
On Windows: `%APPDATA%/Claude/claude_desktop_config.json`
```json
{
"mcpServers": {
" MCP Server for Calling Api": {
"command": "/path/to/ MCP Server for Calling Api/build/index.js"
}
}
}
```
### Debugging
Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector), which is available as a package script:
```bash
npm run inspector
```
The Inspector will provide a URL to access debugging tools in your browser.
TDQS
Scored across 7 tools
The HTTP methods (get, post, put, delete) are clearly distinct, but auth_login and clear_user/list_user overlap in user/token management, which could cause confusion. The descriptions help clarify, but there is some functional overlap in the authentication tools.
The HTTP methods use simple verbs (get, post, put, delete), while the user/token tools use verb_noun patterns (auth_login, clear_user, list_user). This mixed convention is readable but inconsistent, with no uniform pattern across all tools.
With 7 tools, the count is well-scoped for an API server covering core HTTP operations and basic authentication management. Each tool has a clear purpose, and the number is neither too sparse nor excessive for the domain.
The toolset covers essential HTTP methods (GET, POST, PUT, DELETE) and basic authentication lifecycle (login, list, clear), but lacks advanced features like token refresh or error handling. Minor gaps exist, but agents can work around them for most API interactions.