Payman AI Documentation MCP Server
# Payman AI Documentation MCP Server
MCP server that provides easy access to Payman AI's documentation and helps developers build integrations more efficiently.
## Overview
This repository contains the source code for a Payman documentation MCP server. This server allows AI assistants like Claude or Cursor to access Payman's documentation to help developers with their integration questions. By running this server locally, you can enhance your AI assistant's ability to provide accurate and helpful information about Payman's capabilities.
## Prerequisites
- [Node.js](https://nodejs.org/) (v14 or higher)
- [npm](https://www.npmjs.com/) or [yarn](https://yarnpkg.com/)
- Git
## Installation
1. Clone the repository:
```bash
git clone https://github.com/Vanshika-Rana/payman-mcp-server.git
```
2. Navigate to the project directory:
```bash
cd payman-mcp-server
```
3. Install dependencies:
```bash
npm install
# OR
yarn install
```
## Building the Project
Build the TypeScript code into JavaScript:
```bash
npm run build
# OR
yarn build
```
## Checking Server
Check if the server is properly setup:
```bash
node /ABSOLUTE/PATH/TO/PARENT/FOLDER/payman-mcp-server/build/index.js
```
If everything is good, you can now add the Payman MCP server to any client.
- For Claude Desktop: [Here](https://modelcontextprotocol.io/quickstart/server#claude-for-desktop-integration-issues)
- For Cursor: [Here](https://docs.cursor.com/context/model-context-protocol)
TDQS
Scored across 5 tools
The tools have overlapping purposes that could cause confusion, particularly between get-documentation and search-documentation (both retrieve documentation content) and between get-sdk-help and solve-problem (both address integration issues). However, the descriptions provide some differentiation by specifying topics vs. search and SDK usage vs. general issues, which helps mitigate misselection.
All tool names follow a consistent verb_noun pattern with hyphens (e.g., get-code-examples, search-documentation). There are no deviations in naming conventions, making the set predictable and readable throughout.
With 5 tools, the server is well-scoped for its purpose of providing PaymanAI documentation and integration support. Each tool appears to serve a distinct role in the workflow, and the count is neither too sparse nor excessive for the domain.
The tool surface covers key documentation and integration support needs, including code examples, documentation retrieval, SDK help, search, and problem-solving. A minor gap exists in lacking tools for updating or managing documentation (e.g., edit or feedback functions), but agents can likely work around this for the server's stated purpose.