@haven_ai/mcp 0.1.0-alpha

package/dist/index.d.cts

@@ -0,0 +1,80 @@
+import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
+import { HavenClient } from '@haven_ai/sdk';
+import { z } from 'zod/v3';
+
+interface HavenCredentialFile {
+    apiKey: string;
+    delegateKey: string;
+    agentId?: string;
+    safeAddress?: string;
+    apiUrl?: string;
+    /**
+     * Absolute path the credentials were loaded from, if any. Set when the
+     * caller pointed at a JSON file via `--credentials` or `HAVEN_CREDENTIALS`;
+     * left undefined when credentials came purely from environment variables.
+     * The MCP server uses this to locate the consent sidecar
+     * (`<sourcePath>.ack.json`) so `--ack` works regardless of how the
+     * credential path was supplied.
+     */
+    sourcePath?: string;
+}
+/**
+ * Load Haven agent credentials for the MCP server.
+ *
+ * Resolution order — earlier sources win, later sources are fallbacks:
+ *
+ *   1. Explicit `path` argument (typically from `--credentials <path>`).
+ *   2. `HAVEN_CREDENTIALS` env var pointing at a credential JSON file.
+ *   3. Inline env vars: `HAVEN_API_KEY` + `HAVEN_DELEGATE_KEY` (+ optional
+ *      `HAVEN_AGENT_ID`, `HAVEN_SAFE_ADDRESS`, `HAVEN_API_URL`).
+ *
+ * The inline-env path exists so that runtime config snippets emitted by the
+ * Haven dashboard (Claude Desktop / Cursor / generic MCP configs) can be a
+ * single self-contained block — paste the snippet, restart the runtime, done.
+ * The values still live only in the agent operator's process environment;
+ * Haven's backend never sees the delegate key either way.
+ */
+declare function loadCredentials(path?: string | undefined): Promise<HavenCredentialFile>;
+
+type HavenMcpToolName = 'haven_quote_x402' | 'haven_pay_x402_quote' | 'haven_resume_x402_payment' | 'haven_quote_mpp' | 'haven_pay_mpp_challenge' | 'haven_resume_mpp_payment' | 'haven_get_payment_status' | 'haven_get_resume_state' | 'haven_get_agent' | 'haven_get_allowances' | 'haven_list_receipts';
+declare const toolSchemas: Record<HavenMcpToolName, z.ZodRawShape>;
+declare const toolDescriptions: Record<HavenMcpToolName, string>;
+interface ToolSuccess<T> {
+    success: true;
+    data: T;
+}
+interface ToolFailure {
+    success: false;
+    code: string;
+    message: string;
+    statusCode?: number;
+    paymentId?: string;
+    status?: string;
+    phase?: string;
+    nextAction?: string;
+    resume_state?: unknown;
+    body?: unknown;
+}
+type ToolPayload<T = unknown> = ToolSuccess<T> | ToolFailure;
+declare function createToolHandlers(haven: HavenClient): Record<HavenMcpToolName, (input: unknown) => Promise<ToolPayload>>;
+
+interface HavenMcpServerOptions {
+    credentialsPath?: string;
+    credentials?: HavenCredentialFile;
+    /**
+     * When true, write the consent sidecar file (`<credentials>.ack.json`)
+     * with the current consent hash and proceed. Surfaced via the `--ack`
+     * CLI flag.
+     */
+    writeAck?: boolean;
+    /**
+     * When true, skip the consent gate entirely. Reserved for tests and
+     * controlled embedding — production CLIs should not set this.
+     */
+    skipConsent?: boolean;
+}
+declare function createHavenClient(options?: HavenMcpServerOptions): Promise<HavenClient>;
+declare function createHavenMcpServer(options?: HavenMcpServerOptions): Promise<McpServer>;
+declare function runStdioServer(options?: HavenMcpServerOptions): Promise<void>;
+
+export { type HavenCredentialFile, type HavenMcpServerOptions, type HavenMcpToolName, type ToolFailure, type ToolPayload, type ToolSuccess, createHavenClient, createHavenMcpServer, createToolHandlers, loadCredentials, runStdioServer, toolDescriptions, toolSchemas };

package/dist/index.d.ts

@@ -0,0 +1,80 @@
+import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
+import { HavenClient } from '@haven_ai/sdk';
+import { z } from 'zod/v3';
+
+interface HavenCredentialFile {
+    apiKey: string;
+    delegateKey: string;
+    agentId?: string;
+    safeAddress?: string;
+    apiUrl?: string;
+    /**
+     * Absolute path the credentials were loaded from, if any. Set when the
+     * caller pointed at a JSON file via `--credentials` or `HAVEN_CREDENTIALS`;
+     * left undefined when credentials came purely from environment variables.
+     * The MCP server uses this to locate the consent sidecar
+     * (`<sourcePath>.ack.json`) so `--ack` works regardless of how the
+     * credential path was supplied.
+     */
+    sourcePath?: string;
+}
+/**
+ * Load Haven agent credentials for the MCP server.
+ *
+ * Resolution order — earlier sources win, later sources are fallbacks:
+ *
+ *   1. Explicit `path` argument (typically from `--credentials <path>`).
+ *   2. `HAVEN_CREDENTIALS` env var pointing at a credential JSON file.
+ *   3. Inline env vars: `HAVEN_API_KEY` + `HAVEN_DELEGATE_KEY` (+ optional
+ *      `HAVEN_AGENT_ID`, `HAVEN_SAFE_ADDRESS`, `HAVEN_API_URL`).
+ *
+ * The inline-env path exists so that runtime config snippets emitted by the
+ * Haven dashboard (Claude Desktop / Cursor / generic MCP configs) can be a
+ * single self-contained block — paste the snippet, restart the runtime, done.
+ * The values still live only in the agent operator's process environment;
+ * Haven's backend never sees the delegate key either way.
+ */
+declare function loadCredentials(path?: string | undefined): Promise<HavenCredentialFile>;
+
+type HavenMcpToolName = 'haven_quote_x402' | 'haven_pay_x402_quote' | 'haven_resume_x402_payment' | 'haven_quote_mpp' | 'haven_pay_mpp_challenge' | 'haven_resume_mpp_payment' | 'haven_get_payment_status' | 'haven_get_resume_state' | 'haven_get_agent' | 'haven_get_allowances' | 'haven_list_receipts';
+declare const toolSchemas: Record<HavenMcpToolName, z.ZodRawShape>;
+declare const toolDescriptions: Record<HavenMcpToolName, string>;
+interface ToolSuccess<T> {
+    success: true;
+    data: T;
+}
+interface ToolFailure {
+    success: false;
+    code: string;
+    message: string;
+    statusCode?: number;
+    paymentId?: string;
+    status?: string;
+    phase?: string;
+    nextAction?: string;
+    resume_state?: unknown;
+    body?: unknown;
+}
+type ToolPayload<T = unknown> = ToolSuccess<T> | ToolFailure;
+declare function createToolHandlers(haven: HavenClient): Record<HavenMcpToolName, (input: unknown) => Promise<ToolPayload>>;
+
+interface HavenMcpServerOptions {
+    credentialsPath?: string;
+    credentials?: HavenCredentialFile;
+    /**
+     * When true, write the consent sidecar file (`<credentials>.ack.json`)
+     * with the current consent hash and proceed. Surfaced via the `--ack`
+     * CLI flag.
+     */
+    writeAck?: boolean;
+    /**
+     * When true, skip the consent gate entirely. Reserved for tests and
+     * controlled embedding — production CLIs should not set this.
+     */
+    skipConsent?: boolean;
+}
+declare function createHavenClient(options?: HavenMcpServerOptions): Promise<HavenClient>;
+declare function createHavenMcpServer(options?: HavenMcpServerOptions): Promise<McpServer>;
+declare function runStdioServer(options?: HavenMcpServerOptions): Promise<void>;
+
+export { type HavenCredentialFile, type HavenMcpServerOptions, type HavenMcpToolName, type ToolFailure, type ToolPayload, type ToolSuccess, createHavenClient, createHavenMcpServer, createToolHandlers, loadCredentials, runStdioServer, toolDescriptions, toolSchemas };