pi-roundtable-mcp 0.2.0 → 0.3.0

package/CHANGELOG.md

@@ -5,6 +5,14 @@ The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ## [Unreleased]
 
+## [0.3.0] - 2026-10-01
+
+### Added
+
+- `Connectors.resolve(serverName)` reads a virtual server by name, and `Connectors.admin` (`gateways()`, `servers()`) shows what ContextForge holds, for a host that manages some servers itself or shows their state.
+- The `REMOTE_MCP` service of `remoteMcp`: the owner's bundles and grants, read only, and `describeGrant(client, grant)`, so a host can show them in its own status view.
+- The types `GatewayState`, `ChannelBundle`, `ChannelGrant`, and `RemoteMcpService`.
+
 ## [0.2.0] - 2026-10-01
 
 ### Added

package/README.md

@@ -90,6 +90,8 @@ It provides the `CONNECTORS` service (`Connectors`):
 | `servers()` | The virtual servers (name, URL, tool names) of the connectors that could be read |
 | `profileSources()` | One `{ name, description, serverName }` per connector, the shape a host builds a per-agent MCP profile from |
 | `token` | The bearer token that the virtual servers' URLs expect; one per process, valid for a year |
+| `resolve(serverName)` | Reads one virtual server's URL and tools by name, for servers the host manages itself rather than as connectors |
+| `admin` | `gateways()` and `servers()`: what ContextForge holds, upstream gateways with their state and every virtual server with its tool names, for a host's status view |
 
 The plugin does not decide which agent uses which connector.
 The host reads the service, builds its own profiles, and compares `version` with the one it built at.
@@ -177,6 +179,13 @@ The owner grants channels on Discord with `/<root> mcp`:
 | `describe` | Changes the channel name and purpose that the agent sees (Discord's own name and topic stay) |
 | `token` | Replaces a bundle's MCP URL; the old one stops working at once and the channel settings stay |
 
+The plugin provides the `REMOTE_MCP` service (`RemoteMcpService`) for a host that shows the owner what outside agents may reach:
+
+| Member | What it is |
+| --- | --- |
+| `grants` | `bundles()` and `grants(bundleId?)`, read only: every bundle, and the channel grants of one bundle or of all |
+| `describeGrant(client, grant)` | One grant as lines of text for a Discord message: the name the agent sees, where the channel is, its purpose, and the allowed operations, in the plugin's wording |
+
 #### The default conversation
 
 Without `answer` and `claim`, a relayed turn runs on the core: `context.turns.run` of kind `remote`, for an owner-tier speaker, in the channel `mcp:<session>`, through the agent server's runtime.

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "pi-roundtable-mcp",
-	"version": "0.2.0",
+	"version": "0.3.0",
 	"description": "MCP connectors through ContextForge and a remote MCP endpoint for pi-roundtable",
 	"type": "module",
 	"license": "MIT",

package/src/connectors/connectors-plugin.ts

@@ -54,6 +54,10 @@ export interface Connectors {
 	profileSources(): ConnectorProfileSource[];
 	/** The bearer token that ContextForge's virtual server URLs expect; one per process. */
 	readonly token: string;
+	/** Reads a virtual server's endpoint and tools by name, for the servers a host manages itself. */
+	resolve(serverName: string): Promise<VirtualServer>;
+	/** What ContextForge holds, upstream gateways and virtual servers, for a host's status view. */
+	readonly admin: Pick<ContextForgeAdmin, "gateways" | "servers">;
 }
 
 export const CONNECTORS = serviceKey<Connectors>(
@@ -89,9 +93,11 @@ export function mcpConnectors(options: McpConnectorsOptions): RoundtablePlugin {
 		setup: async ({ database, services, logger }) => {
 			const { jwtSecret, user } = options.contextForge;
 			const token = contextForgeToken(jwtSecret, user, TOKEN_TTL_SECONDS);
+			const admin = new ContextForgeAdmin(url, token);
+			const resolve = (name: string) => resolveVirtualServer(url, token, name);
 			const registry = await ConnectorRegistry.attach(database(), {
-				admin: new ContextForgeAdmin(url, token),
-				resolve: (name) => resolveVirtualServer(url, token, name),
+				admin,
+				resolve,
 				logger,
 				serverPrefix: options.serverPrefix ?? DEFAULT_SERVER_PREFIX,
 				maxToolName: options.maxToolName ?? DEFAULT_MAX_TOOL_NAME,
@@ -107,6 +113,11 @@ export function mcpConnectors(options: McpConnectorsOptions): RoundtablePlugin {
 				servers: () => registry.servers(),
 				profileSources: () => registry.profileSources(),
 				token,
+				resolve,
+				admin: {
+					gateways: () => admin.gateways(),
+					servers: () => admin.servers(),
+				},
 			});
 			return {};
 		},

package/src/index.ts

@@ -11,8 +11,12 @@ export type {
 	McpConnectorsOptions,
 } from "./connectors/connectors-plugin.ts";
 export { CONNECTORS, mcpConnectors } from "./connectors/connectors-plugin.ts";
-export type { UpstreamAuth } from "./connectors/contextforge.ts";
+export type { GatewayState, UpstreamAuth } from "./connectors/contextforge.ts";
 export type { ConnectorMessages } from "./connectors/messages.ts";
+export type {
+	ChannelBundle,
+	ChannelGrant,
+} from "./remote-mcp/channel-grants.ts";
 export type {
 	RemoteMcpMessages,
 	RemoteToolNames,
@@ -24,3 +28,5 @@ export type {
 	RemoteMcpOptions,
 } from "./remote-mcp/remote-mcp-plugin.ts";
 export { remoteMcp } from "./remote-mcp/remote-mcp-plugin.ts";
+export type { RemoteMcpService } from "./remote-mcp/remote-mcp-service.ts";
+export { REMOTE_MCP } from "./remote-mcp/remote-mcp-service.ts";

package/src/remote-mcp/remote-mcp-plugin.ts

@@ -26,6 +26,7 @@ import {
 } from "./messages.ts";
 import { RemoteAgent } from "./remote-agent.ts";
 import { type RemoteClaimHooks, remoteClaim } from "./remote-claim.ts";
+import { REMOTE_MCP, remoteMcpService } from "./remote-mcp-service.ts";
 import { RemoteSessionStore } from "./remote-session-store.ts";
 import { RemoteSessionSweeper } from "./session-sweeper.ts";
 
@@ -104,6 +105,7 @@ function checkOptions(options: RemoteMcpOptions): void {
  * An MCP server over HTTP for outside agents: `/mcp/personal` relays turns to the owner's agent
  * and returns the result when polled, and `/mcp/discord/<token>` offers the Discord channel
  * tools granted to one bundle. Grants are approved on Discord with `/<root> mcp`.
+ * Provides `REMOTE_MCP`.
  */
 export function remoteMcp(options: RemoteMcpOptions): RoundtablePlugin {
 	checkOptions(options);
@@ -112,6 +114,7 @@ export function remoteMcp(options: RemoteMcpOptions): RoundtablePlugin {
 	return definePlugin({
 		name: "remote-mcp",
 		requires: [DISCORD],
+		provides: [REMOTE_MCP],
 		migrations: [ChannelGrantStore.migration, RemoteSessionStore.migration],
 		setup: async (context) => {
 			const { services, logger, conversations, database } = context;
@@ -142,6 +145,7 @@ export function remoteMcp(options: RemoteMcpOptions): RoundtablePlugin {
 			discord.commands.add(
 				mcpGrantCommands(discord.guard, grants, options.publicUrl, text),
 			);
+			services.provide(REMOTE_MCP, remoteMcpService(grants, text));
 			return {
 				services: [
 					{

package/src/remote-mcp/remote-mcp-service.ts

@@ -0,0 +1,31 @@
+import type { Client } from "discord.js";
+import { serviceKey } from "pi-roundtable";
+import type { ChannelGrant, ChannelGrantStore } from "./channel-grants.ts";
+import { describeGrant } from "./mcp-grant-panels.ts";
+import type { RemoteMcpMessages } from "./messages.ts";
+
+/** What a host reads to show the owner which channels outside agents may use. */
+export interface RemoteMcpService {
+	/** The owner's bundles and their channel grants, read only. */
+	grants: Pick<ChannelGrantStore, "bundles" | "grants">;
+	/** One grant as lines of text: the agent's name for the channel, where it is, its purpose, and the allowed operations. */
+	describeGrant(client: Client, grant: ChannelGrant): Promise<string>;
+}
+
+export const REMOTE_MCP = serviceKey<RemoteMcpService>(
+	"pi-roundtable-mcp.remote-mcp",
+);
+
+/** The service over the plugin's grant store and its wording. */
+export function remoteMcpService(
+	grants: ChannelGrantStore,
+	text: RemoteMcpMessages,
+): RemoteMcpService {
+	return {
+		grants: {
+			bundles: () => grants.bundles(),
+			grants: (...args) => grants.grants(...args),
+		},
+		describeGrant: (client, grant) => describeGrant(client, grant, text),
+	};
+}