A path, resolved against this Officer, so the agent reaches /api/openseo/mcp
through the same gate as everything else and never the instance directly.
Not wrapped as Officer-native tools: the vocabulary moves upstream, a copy would
go stale, and it fails silently — a tool exists that Officer cannot see.
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.
Per the rule for a new plugin: the public gitea repository and its infrastructure
come first, so there is somewhere for the work to land rather than a directory
that becomes a repository later.
What is here is the shape and the two decisions it deliberately does not make —
where the container runs, and whether Officer's agents call OpenSEO's /mcp
directly or Officer wraps it as native tools. Both are the owner's, both are
recorded in the todo this came from, and the scaffold keeps both open by
proxying.
Everything in the README was verified against upstream's compose.yaml and its
own skills rather than its marketing: one container, port 3001 on loopback,
SQLite in a volume, AUTH_MODE=local_noauth, and DATAFORSEO_API_KEY as base64 of
login:password.
pastilhas