pastilhas
10378d08cc
OpenSEO ships its own MCP server and its own web UI, so this plugin holds the address, holds the credential, and is the door. There are no curated routes in front of it and there should not be: proxy-manager's router already records where that leads — a curated surface cannot keep up, and the plugin becomes a worse version of the thing it wraps. The door IS the security model, not a convenience. Upstream self-hosts with AUTH_MODE=local_noauth, so every request reaching the instance is trusted by design and their docs say to put it behind auth. Officer's gate is that auth. Two things follow and neither is optional: nothing here may publish OpenSEO's own port, and /_config is owner-only, because the address alone is enough to bypass this plugin entirely. The iframe therefore points at /api/openseo/ — this Officer's origin — and never at the instance, since an iframe src is a URL anybody can read out of the page and open directly. The probe asks /mcp for tools/list rather than fetching the home page. A web root answers 200 for a great many things that are not this; a JSON-RPC reply carrying tool names is the instance identifying itself. Saving with an empty key field KEEPS the stored one — absent means keep, empty string means clear. Without that distinction, changing the address from a form that cannot display the credential would silently erase it, and it would surface days later as an instance that had stopped answering. One table, deliberately: every project, keyword and crawl lives in the instance, so uninstalling this cannot destroy anybody's research. The skill says so too, because the temptation to cache a project list is exactly what would break it. The skill leads with cost. This is free software over DataForSEO, metered and billed to the owner per lookup, so it tells the agent not to sweep and to say what a thorough answer would spend before spending it. Tags are `Development` and `Homelab`. `Marketing` and `Research` would both be more accurate and neither exists in the union — extending it is a platform change rather than a plugin's to make.
31 lines
1.3 KiB
TypeScript
31 lines
1.3 KiB
TypeScript
import type { AppRegistryMeta } from 'officerdev';
|
|
import { MessageSquare, Settings, TrendingUp } from 'lucide-react';
|
|
import { AppPanel } from './AppPanel';
|
|
import { ChatPanel, ChatPanelHeader } from './ChatPanel';
|
|
import { ConnectionPanel } from './ConnectionPanel';
|
|
|
|
/**
|
|
* Three panels: the app, a chat, and the settings.
|
|
*
|
|
* The app is OpenSEO's own interface through the proxy — there is nothing for this plugin to curate in
|
|
* front of it, and building a worse OpenSEO is the failure mode proxy-manager's router warns about.
|
|
*
|
|
* The chat is worth its share of the screen here because OpenSEO ships an MCP server: the agent has
|
|
* real tools on the other side of it, which is the whole reason this integration is thin.
|
|
*
|
|
* `availableOnPanel: false` — these belong to this plugin's screen, not the generic panel picker. A
|
|
* "Settings" panel offered on somebody's dashboard would be a connection form with no context.
|
|
*/
|
|
export const appRegistryMetas: AppRegistryMeta[] = [
|
|
{ key: 'openseo-app', name: 'OpenSEO', icon: TrendingUp, component: AppPanel, availableOnPanel: false },
|
|
{
|
|
key: 'openseo-chat',
|
|
name: 'Chat',
|
|
icon: MessageSquare,
|
|
component: ChatPanel,
|
|
header: ChatPanelHeader,
|
|
availableOnPanel: false,
|
|
},
|
|
{ key: 'openseo-settings', name: 'Settings', icon: Settings, component: ConnectionPanel, availableOnPanel: false },
|
|
];
|