Rap2

RAP2 MCP Server lets AI programming assistants access RAP2 API documentation and interface management directly, so you can query interfaces, view details, and navigate RAP2 docs within your coding workflow.

How to use

You run the MCP tool and attach it to your AI programming assistant to enable seamless RAP2 API documentation access. Start from your preferred client (Cursor, Claude Desktop, or any MCP-compatible assistant) and configure a RAP2 MCP server connection using the provided command. Once connected, you can search for interfaces by keyword or path, retrieve detailed information for a specific interface, and view repository-wide interfaces without leaving your editor or chat interface.

How to install

Prerequisites: you need Node.js version 18.0.0 or newer and a modern package manager (npm, pnpm, or yarn). You will run a small MCP client tool to expose RAP2 APIs to your AI assistant.

Concrete steps to start using RAP2 MCP Server via npx (no installation required):

npx -y rap2-mcp-tool@latest

Additional configuration and setup

Configure your MCP client to connect to the RAP2 MCP Server by supplying environment details that point at your RAP2 instance. You can also integrate directly inside certain AI assistants by supplying a small JSON configuration that includes the command, arguments, and environment variables.

Example integration snippet for your MCP client (paste into the client’s MCP configuration):

{
  "mcpServers": {
    "rap2": {
      "command": "npx",
      "args": ["-y", "rap2-mcp-tool@latest"],
      "env": {
        "RAP2_BASE_URL": "http://rap2.example.com",
        "RAP2_EMAIL": "your@email.com",
        "RAP2_PASSWORD": "yourpassword"
      }
    }
  }
}

Security, authentication, and session management

RAP2 MCP Server supports multiple authentication methods. You can authenticate with a username/password pair or via Cookie-based authentication. Typical environment variables you may provide include RAP2_BASE_URL, RAP2_EMAIL, and RAP2_PASSWORD. If you use cookie-based login, you can provide RAP2_SID and RAP2_SID_SIG in your environment. The integration can automatically attempt login when needed and retry requests after 401/403 responses.

Logging and performance

The server records structured logs to help debugging and monitoring. You can tail the log file to observe runtime activity, including requests, responses, and errors.

Troubleshooting

Common issues include failed connections or login sessions. Verify that RAP2_BASE_URL is correct, ensure network access to your RAP2 instance is available, and confirm that the RAP2 server supports your chosen authentication method. If you encounter permission or module-not-found errors, re-run the recommended npx command or install the tool globally if desired.

Developer notes

For development and testing, you can start from source, install dependencies, and run the MCP server in development mode. The typical flow includes cloning the project, installing dependencies with npm, and starting the MCP process.

Examples and usage in conversations

In a chat, you can ask to retrieve interface details by ID, search interfaces by keyword, or search by request path. The AI assistant will perform the corresponding MCP tool calls to fetch the information and present it in a readable format.

Available tools

rap2_test_connection

Test the connection to the RAP2 MCP Server and auto-login if needed, ensuring the server is reachable.

rap2_ensure_session

Ensure a valid login session by using environment variables to log in and store the session cookies for future requests.

rap2_debug_login_info

Output a summary of the current login configuration without exposing plaintext passwords for debugging.

rap2_get_interface_by_id

Fetch detailed information for a specific RAP2 interface by its ID, including URL, method, parameters, and response data structure.

rap2_get_repository_interfaces

Retrieve all interfaces within a specified RAP2 repository by repository ID.

rap2_search_interfaces_by_keyword

Search interfaces by a keyword, with optional repository scoping to limit results.

rap2_search_interfaces_by_path

Search interfaces by request path, with optional repository scoping to limit results.