Model Context Protocol server for Jama Connect Software
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"jama-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
This project provides a Model Context Protocol (MCP) server that exposes read-only tools for interacting with a Jama Connect instance. It acts as an MCP wrapper around the official Jama Software py-jama-rest-client library.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in developer-tools
Manage Supabase projects — databases, auth, storage, and edge functions
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.
Asynchronous coordination layer for AI coding agents: identities, inboxes, searchable threads, and advisory file leases over FastMCP + Git + SQLite
MCP Security Weekly
Get CVE alerts and security updates for Jama Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
This project provides a Model Context Protocol (MCP) server that exposes read-only tools for interacting with a Jama Connect instance. It acts as an MCP wrapper around the official Jama Software py-jama-rest-client library.
Disclaimer: This is a third-party, open-source project and is not officially affiliated with or endorsed by Jama Software.
Note: This server currently only supports read-only operations. Write operations may be added in future updates.
This MCP server is intentionally not published as a package on PyPI or other indices. This decision encourages users to:
This approach prioritizes security awareness and user control over convenience, mitigating risks associated with installing potentially unverified third-party packages. Local execution by cloning the repository is the only supported method at this time.
Clone the Repository:
git clone https://github.com/t-j-thomas/jama-mcp-server.git
cd jama-mcp-server
Docker Build:
sudo docker build -t jama-mcp-server .
This will build the docker image using the project's pyproject.tonl & uv.lock configrations
For Build issues due to Certificates for the Jama Rest Client Repo:
If you see an error like certificate verification failed: CAFile, you can optionally
clone the https://github.com/jamasoftware-ps/py-jama-rest-client.git repo into this directory, and uncomment
# py-jama-rest-client = { path = "./py-jama-rest-client", editable = true }
from pyproject.toml file and comment out
py-jama-rest-client = { git = "https://github.com/jamasoftware-ps/py-jama-rest-client.git" }.
Then,
uv sync
sudo docker build -t jama-mcp-server .
Clone the Repository:
git clone https://github.com/t-j-thomas/jama-mcp-server.git
cd jama-mcp-server
Install Dependencies:
Navigate into the server directory and use uv to create a virtual environment and install dependencies.
uv sync
This installs required dependencies, including boto3 if you plan to use AWS Parameter Store for credentials.
The server requires environment variables to connect to your Jama Connect instance using OAuth 2.0. Credentials can be provided directly or fetched securely from AWS Parameter Store.
Authentication Methods:
Direct Environment Variables:
JAMA_URL (Required): The base URL of your Jama Connect instance (e.g., https://yourcompany.jamacloud.com).JAMA_CLIENT_ID (Required for this method): Your Jama API OAuth Client ID.JAMA_CLIENT_SECRET (Required for this method): Your Jama API OAuth Client Secret.JAMA_CLIENT_ID and JAMA_CLIENT_SECRET are set, they will be used directly, and the AWS Parameter Store configuration will be ignored.AWS Parameter Store (Not Supported for Docker):
JAMA_CLIENT_ID and JAMA_CLIENT_SECRET are not both set directly in the environment.JAMA_URL (Required): The base URL of your Jama Connect instance.