How do I use jama-connect?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@jama-connect what test cases are in the Enphase project?" 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.

jama-connect

by kailash-enph

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

jama-connect

Unified Jama Connect package — MCP server + REST API + web viewer + VS Code extension.

Version: 0.5.0 | Repo: github.com/kailash-enph/jama-connect

Features

MCP Server — Jama integration for Windsurf/Devin (stdio transport)
REST API — FastAPI on localhost:8765 with full Jama CRUD
Web Viewer — pre-built static site at /viewer (no Node.js at runtime)
VS Code Extension — rich-text editor for Jama items with TipTap
Daemon Mode — jama-connect --daemon runs MCP + REST in one process
Cache Seed — pre-populated Enphase Jama cache (91 projects, 8500+ items) downloaded from SharePoint on first run
Devin Symlink — jama-post-install creates junction at ~/.devin/mcp-servers/jama-connect
SQLite Cache — FTS5 full-text search, schema v3, TTL invalidation
Cross-platform — Windows, macOS, Linux (pure Python, no WSL needed)

Related MCP server: mcp-xray-cloud

Installation

pip install jama-connect

Or from wheel:

pip install dist/jama_connect-0.5.0-py3-none-any.whl

Post-Install

jama-post-install          # Creates symlink in ~/.devin/mcp-servers/

CLI Commands

Command	What it does
`jama-connect`	MCP server (stdio) for Windsurf/Devin
`jama-connect --daemon`	MCP + REST API in one process (recommended)
`jama-rest`	REST API + web viewer standalone
`jama-editor`	Install VS Code extension
`jama-post-install`	Create symlink in `~/.devin/mcp-servers/`

Running

Daemon Mode (recommended for Devin/Windsurf)

Starts both MCP (stdio) and REST API (port 8765) in one process:

jama-connect --daemon

This is what mcp_config.json uses — no separate jama-rest terminal needed.

REST API Only

jama-rest

Open http://localhost:8765/viewer in your browser.

VS Code Extension

jama-editor                # Installs bundled VSIX to VS Code

Then open VS Code → Jama Editor sidebar. Requires jama-rest or jama-connect --daemon running.

First-Run Cache Seed

On first run (no ~/.jama-mcp-v2/projects/<id>.db exists), jama-connect will:

Check ~/Downloads/, ~/.jama-mcp-v2/, cwd, and system temp for cache_seed.db.gz
If not found, open the SharePoint link in your browser and wait for you to download
After download, auto-find and decompress (44 MB → 321 MB)

This gives you instant access to 91 projects and 8500+ items without a full sync.

MCP Config (for Windsurf/Devin)

{
  "jama-mcp-v2": {
    "command": "jama-connect",
    "args": [],
    "env": {
      "JAMA_URL": "https://enphase.jamacloud.com",
      "JAMA_CLIENT_ID": "your-client-id",
      "JAMA_CLIENT_SECRET": "your-client-secret",
      "JAMA_CACHE_DIR": "~/.jama-mcp-v2",
      "JAMA_REST_PORT": "8765"
    }
  }
}

Credential Auto-Loading

All commands (jama-connect, jama-rest, jama-editor) automatically find credentials from your IDE's MCP config — no need to set env vars manually.

Searched in order (first match wins):

IDE	Config path
Windsurf	`~/.codeium/windsurf/mcp_config.json`
Devin	`~/AppData/Roaming/devin/mcp_config.json`
Claude Desktop	`~/.config/claude/mcp_config.json`
Cursor	`~/.cursor/mcp.json`

Looks for a jama-mcp-v2, jama-connect, or jama entry and reads the env block.

If no config is found, set env vars directly:

set JAMA_CLIENT_ID=your-client-id
set JAMA_CLIENT_SECRET=your-client-secret

Environment Variables

Variable	Default	Purpose
`JAMA_URL`	`https://enphase.jamacloud.com`	Jama instance URL
`JAMA_CLIENT_ID`	auto from mcp_config	OAuth2 client ID
`JAMA_CLIENT_SECRET`	auto from mcp_config	OAuth2 client secret
`JAMA_CACHE_DIR`	`~/.jama-mcp-v2`	Cache directory
`JAMA_REST_PORT`	`8765`	REST API port
`JAMA_MAX_CONCURRENT`	`10`	Jama API concurrency limit
`JAMA_CACHE_SERVER_URL`	(unset)	LAN cache server URL (e.g. `http://SERVER:8866`)

Development

Prerequisites

Python ≥3.12
Node.js ≥18 (build-time only, for viewer)
uv (Python package manager)

Dev Setup

uv sync                            # install Python deps
cd viewer && npm ci                # install viewer deps

Build

.\build-package.ps1                # Windows (viewer + extension + wheel)
./build-package.sh                 # macOS/Linux
uv build                           # wheel only

Test

uv run pytest tests/ -v            # Python tests
cd vscode-extension && npm test    # TypeScript tests

Publish

twine upload --repository-url http://nz-lnx-01/pypi dist/*

Architecture

┌──────────────────────────────────────────────────┐
│         jama-connect (single process)            │
│                                                  │
│  ┌──────────┐  ┌──────────┐  ┌───────────┐      │
│  │ MCP stdio│  │ REST API │  │  Static   │      │
│  │ (tools)  │  │ /api/*   │  │  Viewer   │      │
│  │          │  │ /editor/*│  │  /viewer  │      │
│  └──────────┘  └──────────┘  └───────────┘      │
│              ↕                                   │
│     ┌──────────────────────┐                     │
│     │  SQLite cache.db     │                     │
│     │  (FTS5, schema v3)   │                     │
│     │  + editor_db.sqlite  │                     │
│     └──────────────────────┘                     │
│              ↕                                   │
│     ┌──────────────────────┐                     │
│     │  Jama Cloud API      │                     │
│     │  (OAuth2 + httpx)    │                     │
│     └──────────────────────┘                     │
└──────────────────────────────────────────────────┘

Daemon mode: MCP stdio (main thread) + REST API (background thread)
             → one process, shared cache, shared API client

Files

Location	Purpose
`~/.jama-mcp-v2/projects/<id>.db`	Jama item/test cache
`~/.jama-mcp-v2/editor_db.sqlite`	Editor drafts/schema
`~/.jama-mcp-v2/logs/`	Service logs
`~/.devin/mcp-servers/jama-connect`	Devin symlink/junction

This server cannot be deployed

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Maintenance

ActivityMaintained

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Related MCP Connectors

SmartBear MCPOAuth
com.smartbear
MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J.
Monitoring Testing & QA Tools API Testing
144
OneSchema MCP Server
co.oneschema
MCP server that lets AI assistants use all OneSchema features exposed via the public API.
Data Platforms App Automation
1
Swagger MCPOAuth
com.smartbear
MCP server for AI access to Swagger by SmartBear.
API Testing Documentation Access Developer Tools
144
Artificial Wit AIOAuth
com.artificialwit
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
ERP Systems CRM Knowledge & Memory
2

Related MCP Servers

Personal JIRA MCP
Project Management App Automation
yuezheng2006
A
license
C
quality
C
maintenance
An MCP server that enables AI assistants to interact with JIRA, allowing for querying issue details, creating and updating work items, and managing attachments through a standardized interface.
Updated a year ago (2025-05-20 17:01 UTC)
12
4
MIT
mcp-xray-cloud
Testing & QA Tools Project Management
remynln
A
license
Not graded
quality
D
maintenance
An MCP server that connects AI assistants to Xray Cloud for Jira test management, enabling natural language interaction with tests, test plans, executions, and CI result imports.
Updated 6 months ago (2026-03-09 12:21 UTC)
MIT
jgs-sysmlv2-api-mcp
Software Architecture Autonomous Agents
jgsystemsconsulting
F
license
Not graded
quality
A
maintenance
An MCP server that gives an AI agent read and write access to a live SysML v2 model through the vendor-neutral OMG SysML v2 REST API.
Updated 2 months ago (2026-07-05 20:53 UTC)
2
-
mcp-atlassian
Project Management Content Management Systems Search
matutezam
A
license
Not graded
quality
B
maintenance
MCP server for Atlassian Confluence and Jira, enabling AI assistants to search, create, and update issues and pages via natural language.
Updated 17 days ago (2026-09-02 00:28 UTC)
MIT

jama-connect

Features

Installation

Post-Install

CLI Commands

Running

Daemon Mode (recommended for Devin/Windsurf)

REST API Only

VS Code Extension

First-Run Cache Seed

MCP Config (for Windsurf/Devin)

Credential Auto-Loading

Environment Variables

Development

Prerequisites

Dev Setup

Build

Test

Publish

Architecture

Files

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Personal JIRA MCP

mcp-xray-cloud

jgs-sysmlv2-api-mcp

mcp-atlassian