jameson-entra-mcp
MCP client for Jameson, DataNinja's read-only marketing research server. It signs you in with your
Microsoft work account and forwards your questions to the hosted server. No AWS account, no access
key, nothing in ~/.aws.
Install
claude mcp add jameson --scope user -- uvx jameson-entra-mcp
For Codex:
codex mcp add jameson -- uvx jameson-entra-mcp
Restart your editor, then name Jameson in a question. The first tool call opens a browser tab for a
normal Microsoft sign-in. The token is cached at ~/.jameson-mcp/msal-cache.json and every question
after that is silent. If the server ever rejects the cached token, the client clears
the account and signs you in again once before it reports a failure.
Configuration
Defaults point at the live deployment. Override any of them with environment variables:
| variable | what it is |
|---|---|
JAMESON_MCP_URL |
The MCP endpoint to post to, and the base of the scope requested at sign-in |
JAMESON_TENANT |
Entra tenant id whose tokens the server accepts |
JAMESON_API_APP_ID |
App registration exposing access_as_user |
JAMESON_TOKEN |
A bearer token to present as-is, skipping the sign-in entirely |
JAMESON_TOKEN is the escape hatch for CI and agents, which have no browser.
What it does
It answers initialize, tools/list and ping itself so your editor starts without a sign-in,
then forwards every tools/call to the server with the token attached. Sign-in rides the Azure
CLI's public client id, which is pre-authorized on the API app registration, so there is nothing to
register in Entra on your side.
1 maintainer
Metadata
1 maintainer
Release files for jameson-entra-mcp 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| jameson_entra_mcp-0.3.0.tar.gz | 6.9 kB | Without provenance | Details for jameson_entra_mcp-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| jameson_entra_mcp-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for jameson_entra_mcp-0.3.0-py3-none-any.whl |
Total release size: 14.8 kB
Release files / jameson_entra_mcp-0.3.0.tar.gz
| Download URL | jameson_entra_mcp-0.3.0.tar.gz |
|---|---|
| Size | 6.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
03cf7c4b085dd4ee9cf9a23aef458acf405a60544dad4e71d432febe373cf3d8
|
|
BLAKE2b-256 checksum How to use checksums |
cb2c8351a9bd41c48cced52383720e5b5bedc96fe1970fe01801f5621859cb4a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.11 {"installer":{"name":"uv","version":"0.11.11","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / jameson_entra_mcp-0.3.0-py3-none-any.whl
| Download URL | jameson_entra_mcp-0.3.0-py3-none-any.whl |
|---|---|
| Size | 7.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0ffd42a1165a4e37b4cd31f8e9faf9a309da4c3752fe0c4c6815ae81ad5afbcc
|
|
BLAKE2b-256 checksum How to use checksums |
31d022d3ad74f70cd2d5d701df8e5ffdcb5fc1e416822dcffb47b6de124398f7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.11 {"installer":{"name":"uv","version":"0.11.11","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for jameson-entra-mcp 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
