mcpbundles-mcp-connect
Python client library for MCP Connect Auth on MCPBundles.
connect_auth_callback_identity()— canonicalget-user-infoJSON from a verified FastMCP tokenMcpbundlesConnectProvider— FastMCP auth (interim package export until upstream FastMCP merge)mcpbundles_fastmcp()— one-line FastMCP setup (auth + optional origin handshake telemetry)complete_federation()— finish OAuth federation after your sign-in flowMcpbundlesHandshakeMiddleware— origin initialize cohort ingest when telemetry is enabled
Identity in tool callbacks
Connect Auth separates who signed in (sub, optional organization_id, email, roles) from which MCP client is calling (client_id). Pass email and roles in federation complete to mint them on access tokens.
In FastMCP tools, use connect_auth_callback_identity(get_access_token()) for the same JSON shape as the mcp-use get-user-info example. See Tool callback identity.
Path B — bundle URL only
Publish with MCP Connect Auth, set your federation sign-in URL, and have clients connect via https://mcp.mcpbundles.com/bundle/{slug}. No pip install required on your MCP server.
Path A — vendor origin (FastMCP)
from mcpbundles_mcp_connect import connect_auth_callback_identity, mcpbundles_fastmcp
from fastmcp.server.dependencies import get_access_token
mcp = mcpbundles_fastmcp(
"My App",
listing_slug="my-listing",
base_url="https://mcp.example.com",
)
@mcp.tool
def get_user_info() -> dict:
token = get_access_token()
if token is None:
return {"error": "Not authenticated"}
return connect_auth_callback_identity(token)
After sign-in on your web app, complete federation server-side:
from mcpbundles_mcp_connect import complete_federation
await complete_federation(
listing_slug="my-listing",
federation_secret=os.environ["MCPBUNDLES_FEDERATION_SECRET"],
state=state_from_redirect,
subject=user_id,
organization_id=organization_id,
email=user_email,
roles=user_roles,
)
Full setup guide: https://www.mcpbundles.com/docs/integrations/mcp-connect-auth
pip install mcpbundles-mcp-connect
Metadata
Release files for mcpbundles-mcp-connect 0.1.3
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 | |
|---|---|---|---|---|
| mcpbundles_mcp_connect-0.1.3.tar.gz | 14.1 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcpbundles_mcp_connect-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 27.7 kB
Release files / mcpbundles_mcp_connect-0.1.3.tar.gz
| Download URL | mcpbundles_mcp_connect-0.1.3.tar.gz |
|---|---|
| Size | 14.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bda7891e6ab403150cceaf61b5a53afc78b441a506b74457c211e1a0e10504c9
|
|
BLAKE2b-256 checksum How to use checksums |
b8b2d1e229141df13a67f9b09a8f537125795e025c7938c36e1ddb23a21bd457
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 24, 2026.
Transparency logRelease files / mcpbundles_mcp_connect-0.1.3-py3-none-any.whl
| Download URL | mcpbundles_mcp_connect-0.1.3-py3-none-any.whl |
|---|---|
| Size | 13.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3e4162d5164ed10ec7e04e4471f682c2d30bb41292a72dbad59b78f4a91c3cde
|
|
BLAKE2b-256 checksum How to use checksums |
eb051197fae276ebcc1308e43169a3163d6627d552e22bc5ecb8147c18f9ce07
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 24, 2026.
Transparency logSecurity for mcpbundles-mcp-connect 0.1.3
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for mcpbundles_mcp_connect-0.1.3.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 24, 2026.
Transparency logA 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.