lane-mcp-auth

OAuth 2.1 resource server and consent gate for an MCP server behind Lane — the Python distribution of @getonlane/mcp-auth.

Docs — overview · quickstart · the gate · reference

pip install lane-mcp-auth          # core
pip install 'lane-mcp-auth[fastmcp]'   # + the FastMCP helpers

Your server verifies bearer tokens, publishes the discovery document clients need, and refuses every tool until the caller holds a recorded, revocable grant.

from lane_mcp_auth import LaneMcpAuth

auth = LaneMcpAuth(
    resource="https://acme.example/mcp",
    connections=connections,   # yours: this is server-side state
    exchanger=exchanger,
)

The three tiers

tier	reached by	declared
authenticated only	—	not registrable
any connected caller	completing the step-up	no scope
a specific authority	the step-up granting it	`scope="…"`

Registration is the floor. Omitting a scope means any connected caller, never anyone: a session that has not registered has nothing anyone can revoke, so a tool answering it would be answering something nobody can withdraw.

With FastMCP

from lane_mcp_auth.fastmcp import register_step_up_tool, guarded

register_step_up_tool(mcp, auth)

@mcp.tool()
@guarded(auth, "read_orders", scope="email")
async def read_orders(ctx) -> str:
    return await orders_for(ctx)

Never authorize on the token's scopes

claims.scopes is the token's own claim: empty before the step-up, stale after. Authority lives in the connection and is reachable only through has_scope() / effective_scopes(), because Lane decides it at exchange time and can refuse an exchange it would previously have allowed. A signed claim cannot be withdrawn.

Parity with the TypeScript

Same invariants, same names where Python idiom allows. The TypeScript package is the reference implementation; where the two could drift — scope filtering, the metadata paths, the gate's decision table — see SCOPE.md for what is implemented here and what is not yet.

Licence

MIT

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

lane_mcp_auth-0.1.7.tar.gz (140.7 kB view details)

Uploaded Aug 26, 2026 Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

The dropdown lists show the available interpreters, ABIs, and platforms. Enable javascript to be able to filter the list of wheel files.

lane_mcp_auth-0.1.7-py3-none-any.whl (16.5 kB view details)

Uploaded Aug 26, 2026 Python 3

File details

Details for the file lane_mcp_auth-0.1.7.tar.gz.

File metadata

Download URL: lane_mcp_auth-0.1.7.tar.gz
Upload date: Aug 26, 2026
Size: 140.7 kB
Tags: Source
Uploaded using Trusted Publishing? Yes
Uploaded via: twine/7.0.0 CPython/3.13.14

File hashes

Hashes for lane_mcp_auth-0.1.7.tar.gz
Algorithm	Hash digest
SHA256	`2b62f60b0f692e2280e999a233d54eca9c070f6e2dd2b5f22f912d492c5975f4`
MD5	`0b8eabbe6a64bdccb02dc2576ea18922`
BLAKE2b-256	`b7b8e368bf8ca7123f862a4430e456b6aec585a436f1c3b396b5722dfdc4476a`

See more details on using hashes here.

Provenance

The following attestation bundles were made for lane_mcp_auth-0.1.7.tar.gz:

Publisher: publish-mcp-auth.yml on Lane-Technologies-Inc/lane

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Statement:
- Statement type: https://in-toto.io/Statement/v1
- Predicate type: https://docs.pypi.org/attestations/publish/v1
- Subject name: lane_mcp_auth-0.1.7.tar.gz
- Subject digest: 2b62f60b0f692e2280e999a233d54eca9c070f6e2dd2b5f22f912d492c5975f4
- Sigstore transparency entry: 2597282636
- Sigstore integration time: Aug 26, 2026
Source repository:
- Permalink: Lane-Technologies-Inc/lane@10e475c0258f8d18b4ebbfcd01c240a8ff781163
- Branch / Tag: refs/heads/main
- Owner: https://github.com/Lane-Technologies-Inc
- Access: private
Publication detail:
- Token Issuer: https://token.actions.githubusercontent.com
- Runner Environment: github-hosted
- Publication workflow: publish-mcp-auth.yml@10e475c0258f8d18b4ebbfcd01c240a8ff781163
- Trigger Event: workflow_dispatch