Jotai

Provides MCP endpoints for Jotai atom-based data using Deno and GitHub access.
  • typescript

29

GitHub Stars

typescript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "jotaijs-jotai-mcp-server": {
      "command": "deno",
      "args": [
        "run",
        "--allow-env",
        "--allow-net",
        "npm:jotai-mcp-server"
      ],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "your_github_token"
      }
    }
  }
}

You can run the Jotai MCP Server to expose your Jotai atom data as MCP endpoints that clients can consume locally or over a network. This server runs under Deno and uses your GitHub token to authenticate and fetch data from the upstream Jotai sources as needed.

How to use

Start the server in a local or deployment environment and connect your MCP client to the running process. You’ll provide the GitHub token so the server can access protected sources. Run the server as a stdio MCP server, then initiate client requests to fetch or synchronize Jotai atoms through the MCP protocol. Keep the server running to serve multiple client requests, and monitor the console for startup messages and potential errors.

How to install

Prerequisites: ensure Deno is installed on your system.

Configure the server with your GitHub token and start it using the runtime command shown in the code example.

{
  "mcpServers": {
    "jotai-mcp-server": {
      "command": "deno",
      "args": ["run", "--allow-env", "--allow-net", "npm:jotai-mcp-server"],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "your_github_token"
      }
    }
  }
}

Notes and configuration details

The server is started as a standard input/output (stdio) MCP server. It runs via Deno and uses the npm:m jotai-mcp-server package under the hood. Ensure the environment variable GITHUB_PERSONAL_ACCESS_TOKEN is set to a valid token before starting the server.

Security and environment

Protect your GitHub token. Do not commit the token or expose it in logs. Prefer running the server in a secure environment and limit network exposure to trusted clients only.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational