Gateway

works.jinnPublished by jinn.worksOfficial publisherv1.0.0Updated Oct 28, 2026

Jinn gateway MCP — brand DNA, brand kits, design systems, and agency tools behind one bearer token.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Remote Jinn gateway MCP that gives an assistant access to brand DNA, brand kits, design systems and agency tools through one bearer token.

What you can do
  • Access brand DNA, brand kits and design systems through the Jinn gateway.
  • Use agency tools exposed by the gateway alongside brand assets.
  • Authenticate once with a bearer token rather than per-service credentials.
  • No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Worth adding when an assistant needs to work with a Jinn account's brand assets, design systems or agency tooling, and you are comfortable connecting to a hosted endpoint with a token.
Requirements
A remote streamable HTTP endpoint at app.jinn.works; no local package or runtime. OAuth authentication is required, with an Authorization header carrying a bearer jmcp_ token requested from the provider's documentation page. Network access to the endpoint.
Before you install
The Authorization header holds a secret bearer token; keep it private and revocable. The manifest lists no tools, so what the assistant can read or change is not verifiable before connecting. Requests and any brand or design data go to the third-party Jinn service.

Installation

In SourceWeft

  1. Open Gateway in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/works.jinn%2Fgateway/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "gateway": {
      "type": "http",
      "url": "https://app.jinn.works/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.