@agentlogin/mcp 0.0.0-stage → 0.2.0-beta.1

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -1,3 +1,233 @@
-# Temporary Holding Version
+# @agentlogin/mcp
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+Local MCP tools for Agent Login. A configured agent enrolls its key, signs in to a
+configured application, and uses that application's session through the same helper.
+Private keys, enrollment polling credentials, assertions, authorization codes and
+cookies stay in the local process and private state directory. This does not sign a
+separate browser in.
+
+This package targets the pinned draft in [the compatibility worklist](../../docs/draft-0.2-status.md).
+It is an implementation, not a conformance certification. No provider is preferred.
+
+## Install and configure
+
+Use Node.js 22.23.4 or a supported later release. The beta package version is
+`0.2.0-beta.1`. After that exact release is published, install it without selecting
+the `latest` tag:
+
+```sh
+npm install --save-exact @agentlogin/mcp@0.2.0-beta.1
+```
+
+For development or release rehearsal, install the matching locally packed
+`agentlogin` and `@agentlogin/mcp` tarballs together. A build does not publish them:
+
+```sh
+npm install /absolute/artifacts/agentlogin-0.2.0-beta.1.tgz /absolute/artifacts/agentlogin-mcp-0.2.0-beta.1.tgz
+```
+
+Copy [the example configuration](examples/config.json), replace the reserved example
+domains and absolute paths, and set the file to mode `0600`. The state directory must
+be owned by the launching user with mode `0700`. Run:
+
+```sh
+./node_modules/.bin/agentlogin-mcp --check-config /absolute/private/agentlogin.json
+```
+
+Add a local stdio server to the MCP host. Use absolute executable and config paths;
+use the host's protected environment/secret facility for enrollment API credentials.
+
+```json
+{
+  "mcpServers": {
+    "agentlogin": {
+      "command": "/absolute/project/node_modules/.bin/agentlogin-mcp",
+      "args": ["--config", "/absolute/private/agentlogin.json"]
+    }
+  }
+}
+```
+
+The helper accepts current MCP 2026-07-28 and the SDK's supported legacy protocols.
+It uses the official server SDK. Both modern and legacy stdio clients are exercised
+in the package tests. stdout is exclusively the MCP channel during serving.
+
+## Operator configuration
+
+`identities` names the handles the user may use. Discovery establishes the issuer;
+an optional explicit `issuer` pins a known deployment. A moved handle must be
+re-enrolled at its new issuer. `ownerPortal` identifies the trusted human portal.
+An optional `ownerApprovalPath`, such as `/identity/transactions/{transaction_id}`,
+derives a direct approval link from that portal's origin and the validated,
+nonsecret transaction identifier. It never uses an issuer-supplied action URL.
+
+`applications` is an explicit target allowlist. Every entry has one exact `origin`,
+a `loginPath`, and a JSON `sessionCheck` endpoint with JSON Pointers for the
+authenticated handle, issuer and immutable subject. A callback response alone is
+not evidence of authentication. Fresh sign-in first discards the previous local
+jar, then requires the session issuer to match actual discovery and the completed
+sign-in. Its `(issuer, subject, handle)` binding is saved privately and must match
+on every application operation. Discovery is rechecked within its protocol cache
+lifetime; a changed issuer selects a new session namespace and requires sign-in.
+An unbound cookie jar from an earlier helper version also requires fresh sign-in.
+
+Each named application operation fixes the HTTP method and path, accepted input
+field names, and selected JSON output fields. Write operations use `inputFields`
+for JSON body fields. GET operations may instead declare `queryFields`; their
+inputs must be strings and are encoded as query parameter values. They cannot
+replace query parameters already fixed in the configured path. Input is bounded
+to 32 KiB. No tool accepts an arbitrary URL,
+headers, cookie or bearer token. Responses are bounded to 64 KiB and only configured
+fields are returned; known cookie values and credential-shaped fields are redacted.
+Configure business-data endpoints, not token/debug/export endpoints. This redaction
+is defense in depth, not a way to safely publish arbitrary secret-bearing responses.
+The application must enforce its own authorization and CSRF protections.
+
+The example `list_notes` operation returns one bounded page with `next_cursor`.
+For the next page, pass that opaque cursor as `input: { "before": "<next_cursor>" }`
+to the same operation. Stop when `next_cursor` is null. Pagination keeps each
+notes response within the helper's 64 KiB response limit.
+
+HTTP is permitted only for explicitly configured loopback URLs when
+`developmentLoopback` is true. Production configuration uses HTTPS. Catalogs do not
+alter this configuration or cause a listed issuer/application to be trusted.
+
+## Tool flow
+
+1. `agentlogin_inventory` lists identities, applications and operations.
+2. If the identity needs a key, `agentlogin_enroll` begins or resumes enrollment.
+   `agentlogin_enrollment_status` reports the public Owner approval link and outcome.
+3. `agentlogin_sign_in` returns an operation identifier promptly.
+4. Poll `agentlogin_status` no faster than its suggested interval. An
+   `awaiting_consent` result contains the scopes, disclosure, client identifier,
+   redirect host, client name, terms/privacy URLs and reason for review. These
+   metadata strings are bounded untrusted text; links are not opened automatically. After the
+   user's authorization, `agentlogin_review` allows or denies it. An
+   `awaiting_owner` result supplies the transaction identifier and, when configured,
+   a direct human approval link. It requires the real Owner's independent approval; an MCP
+   review cannot provide it.
+5. After `authenticated`, call `agentlogin_request` for user-authorized operations.
+   Each request checks the current application session. It never follows an
+   application redirect or retries a write. For idempotent APIs such as the example
+   notes app, preserve the same input `id` for an explicitly requested retry after
+   an uncertain network result.
+6. `agentlogin_logout` invokes the configured application logout endpoint and clears
+   the local jar only after a 2xx response. It does not revoke the agent key or a
+   separate browser session.
+
+Sign-in is bounded to 180 seconds by default (configurable from 10 to 600). Up to
+four sign-in/request operations run concurrently, with only one per identity and
+application. Duplicate sign-in starts reuse the live operation; new attempts have
+a five-second cooldown. Tool calls have a 60-call burst and refill at one per second.
+The issuer's poll intervals and 429 responses are respected by the SDK. Each
+sign-in task has a fixed seven-day `decisionExpiresAt`. A local deadline pauses
+network work without deleting that task. Its protected record survives restart;
+`agentlogin_status` returns `paused` and `resumable: true` while time remains.
+Explicitly call `agentlogin_sign_in` for the same pair to resume. The `intent`
+identifier stays the same, but the `operation` identifier and Core transaction are
+fresh, so a delayed review of old terms cannot approve a new disclosure.
+
+This retains the task, not its old disclosure, consent, Owner approval, callback
+URL or transaction authority. Current terms and any required Owner approval are
+checked again. A paused task never displays an old Owner transaction link. Changing
+its configured identity/application or discovered issuer fails closed and requires
+the operator to resolve the saved task. After seven days, an explicit new sign-in
+creates a new intent rather than extending the expired one. One current task record
+is kept per configured pair. Completed in-memory summaries expire after fifteen
+minutes and the history is capped at 128.
+
+## Enrollment broker integration
+
+Core enrollment continues to use the issuer's proof-of-possession protocol. An
+optional hosted broker allows the human to approve the generated public key without
+putting an Owner Credential in an agent tool call. Configure `enrollmentEndpoint`
+and `enrollmentCredentialEnv` on an identity. The latter names an injected provider
+API credential; it is sent only to the exact configured endpoint, without redirects.
+
+The broker contract used by the SentFrom.ai integration is:
+
+| Request | Result |
+| --- | --- |
+| `POST enrollmentEndpoint`, provider bearer credential; `{handle, public_jwk, name}` | `201` with `{request_id, approval_url, polling_token, expires_at}` |
+| `GET enrollmentEndpoint/{request_id}`, polling bearer credential | `200` with `status` `pending`, `approved`, `denied` or `expired`; optional `retry_after` |
+| Approved response | `enrollment` contains `kid`, `status`, `expires_at`; a pending proof also contains `challenge`, `proof_url` |
+
+`approval_url` must be exactly the configured endpoint's origin and path followed
+by `/{request_id}/approve`, without query or fragment. The identifier is not approval
+authority. The human authenticates separately. The helper checks the approved `kid`,
+checks `proof_url` against discovered issuer metadata, and signs the Core enrollment
+proof locally. This broker is a product integration, not an addition to Core.
+
+The pending request, polling credential and key survive process restarts in mode
+`0600` files. SentFrom's provider decision window is seven days; the returned
+`expires_at` is authoritative and explicit resumes do not extend it. Local polling
+is bounded by `signInTimeoutSeconds`, not the human decision window. Reaching
+that local limit returns `awaiting_owner` with `polling: false` and
+`resumable: true`, without deleting or declining the request. Status after restart
+reads the saved record without network traffic. Stop polling when `polling` is
+false; explicitly call `agentlogin_enroll` to check and resume the same request.
+After Owner approval, the provider can issue a fresh short-lived proof challenge
+when the agent returns; no seven-day signing proof is created. A failed challenge
+is not signed twice in one run.
+
+An explicitly configured `issuer` supports initial enrollment through validated
+issuer metadata even before the broker creates the handle's issuer record. Its
+`handle_domains` must serve the configured handle. Without an explicit issuer,
+normal handle discovery is required. Broker endpoints and credentials still come
+only from trusted operator configuration. This does not change sign-in discovery.
+
+A lost proof response is reported as `enrollment_uncertain`; an
+explicit retry polls that same request and accepts only the same key's `active`
+status. It does not silently create a replacement identity. Expired/denied requests
+require the operator to resolve or reset the enrollment record before a new request.
+Enrollment runs are bounded and at most two actively poll concurrently. Paused
+requests do not occupy those slots. `denied` and `expired` are terminal and keep
+the pending key for deliberate operator resolution; a changed configuration cannot
+silently replace the saved request.
+
+## State and failure handling
+
+Keys and per-identity/per-application cookie jars live under `stateDirectory`.
+The session namespace includes the actual handle, discovered issuer and origin,
+not just friendly configuration names. Clearing cookies for fresh sign-in does not
+revoke the former server session; use logout for server-side invalidation. One
+serving process owns a directory at a time.
+Never remove its lock while that process can resume. After an unclean crash, stop
+all helpers before removing the abandoned `mcp-server.lock`.
+
+The local filesystem must provide the atomic file operations the SDK requires.
+This directory is not a multi-host storage adapter. Each local agent has its own
+keys/sessions; the hosted issuer and application use their separate shared databases.
+When the host closes stdio, the helper exits and stops pending network work.
+Sign-in task records, keys, enrollment requests and application cookies survive
+restart. Resuming a sign-in task uses a new protocol transaction and operation
+identifier; credentials and decisions from the old attempt are never restored.
+A failed or uncertain operation is never labelled successful.
+
+Install [the skill](skills/agent-login/SKILL.md) if the host supports skills. The skill
+explains consent and output boundaries; endpoint access is enforced by the helper.
+
+## Catalogs and verification
+
+`agentlogin_catalog` reads explicitly configured, locally reviewed catalog files.
+Validate a file with `agentlogin-mcp --check-catalog /absolute/catalog.json`.
+See [catalog policy and format](../../catalogs/README.md) for evidence requirements.
+The provider list includes unreviewed candidates; candidate status supplies no
+review evidence or automatic trust. AgentID entries describe a separate OIDC
+integration and require the [AgentID adapter](../agentid-mcp/README.md); this Core
+helper does not treat those listings as compatible issuer metadata.
+Application listings distinguish open metadata clients from registered clients, whose
+opaque identifiers are scoped to their exact registering issuer. Neither form changes
+the helper's explicit application or identity configuration.
+
+Run `node --import tsx --test packages/mcp/test/*.test.ts` after the workspace build.
+The suite covers the real stdio protocol, input validation, disclosure decisions,
+callback and session binding, request limits, response redaction, concurrency,
+enrollment recovery, catalogs and private storage. Whole-release clean-consumer
+testing is run separately by the repository release checks.
+
+Upstream references checked for this implementation:
+[MCP tools](https://modelcontextprotocol.io/specification/2026-07-28/server/tools),
+[official SDK stdio](https://ts.sdk.modelcontextprotocol.io/v2/serving/stdio.html),
+[legacy clients](https://ts.sdk.modelcontextprotocol.io/v2/serving/legacy-clients.html),
+[Claude plugin manifests](https://code.claude.com/docs/en/plugins-reference).

package/bin/agentlogin-mcp.js

@@ -0,0 +1,3 @@
+#!/usr/bin/env node
+import { main } from '../dist/cli.js';
+await main();