@extenshi/mcp/dist/index.js

Extenshi MCP server — bring the extension catalog (search, security, market research) and pre-publish scanning into your AI tools

#!/usr/bin/env node
/**
 * @extenshi/mcp — Model Context Protocol server for extension developers.
 *
 * Runs locally over stdio inside an MCP client (Claude Code/Desktop, Cursor)
 * and exposes the Extenshi catalog as tools: market-research reads against the
 * public BFF, plus a paid `scan_extension` that reuses the CLI scan path, and a
 * local `publish_extension`.
 *
 * The TOOLS themselves live in `tools.ts` (transport-agnostic) so the sibling
 * remote OAuth server (`@extenshi/mcp-server`) reuses the exact same registry.
 * This file is just the stdio wiring: it injects deps that resolve identity
 * from the environment (one `ek_…` key) and enables ALL capabilities.
 *
 * Auth: an `ek_…` API key is REQUIRED. Over stdio there are no request headers,
 * so the key comes from the environment (EXTENSHI_API_KEY) / `~/.extenshi`
 * config — see config.ts. The backend independently enforces the key, so this
 * is defense in depth, not the only gate.
 *
 * NB: stdout is the MCP protocol channel — never write to it (use stderr).
 */
import { createRequire } from 'node:module';
import { FastMCP, UserError } from 'fastmcp';
import { makeBff } from './bff.js';
import { loadConfig } from './config.js';
import { reportServerStarted } from './startup.js';
import { flushTelemetry, initTelemetry } from './telemetry.js';
import { getServerInstructions, MISSING_KEY_MESSAGE, registerTools, SERVER_NAME, } from './tools.js';
import { checkForUpdate } from './update-check.js';
const require = createRequire(import.meta.url);
const pkg = require('../package.json');
initTelemetry({ surface: 'mcp', version: pkg.version });
const cfg = loadConfig();
/** Return the configured key or refuse with an actionable instruction. */
function requireKey() {
    if (!cfg.apiKey)
        throw new UserError(MISSING_KEY_MESSAGE);
    return cfg.apiKey;
}
/** Build a BFF client bound to the developer's env key (verifies key presence). */
function bff() {
    return makeBff(cfg.bffUrl, requireKey());
}
const capabilities = new Set(['read', 'docs', 'scan', 'publish']);
const server = new FastMCP({
    name: SERVER_NAME,
    // FastMCP types `version` as a semver template literal; package.json gives a plain string.
    version: pkg.version,
    instructions: getServerInstructions(capabilities),
});
// stdio identity is fixed (env key) — the call context is ignored. ALL four
// capabilities are enabled: the local client has a filesystem and store creds.
const stdioDeps = {
    cfg: { bffUrl: cfg.bffUrl, scanUrl: cfg.scanUrl, docsUrl: cfg.docsUrl },
    capabilities,
    getBff: () => bff(),
    requireApiKey: () => requireKey(),
    getApiKey: () => cfg.apiKey ?? undefined,
};
registerTools(server, stdioDeps);
// Flush buffered telemetry on shutdown. 'beforeExit' covers the natural
// stdin-closed exit; SIGTERM/SIGINT (the MCP client killing the server) bypass
// it, so handle those explicitly and then exit. During a session posthog-node's
// interval flush already drains events, so at most the last few seconds are at
// risk. Never blocks: flushTelemetry is hard-capped (~2.5s).
for (const signal of ['SIGTERM', 'SIGINT']) {
    process.once(signal, () => {
        void flushTelemetry().then(() => process.exit(0));
    });
}
process.once('beforeExit', () => {
    void flushTelemetry();
});
// Awaited, unlike the fire-and-forget calls around it. FastMCP's stdio `start()`
// is genuinely async — it awaits `session.connect(transport)` and only then
// registers the close handlers — so calling it and reporting on the next line
// would time the event to "we called start", not "the session connected". It
// resolves once connected rather than on shutdown, so awaiting it does not
// strand the lines below. A rejection stays as loud as it was before: nothing
// catches it, the process dies, and no event is emitted for a server that never
// served. Top-level await is available here (ESM, target ES2022).
await server.start({ transportType: 'stdio' });
// Reaching this line means a client actually EXECUTED the server and the stdio
// session connected: config parsed, tools registered, transport live. That is the
// population `mcp_installed` cannot describe — postinstall counts npm extractions,
// most of which are ecosystem scanners that never run the binary. See
// ./startup.ts for the measurement.
reportServerStarted(cfg.apiKey);
// Fire-and-forget: nudge to stderr if a newer version is on npm. Never blocks
// startup, never touches stdout (the MCP channel), fully fail-soft.
void checkForUpdate(pkg.version);
//# sourceMappingURL=index.js.map