Tengence GEO Agent
GEO/SEO content pipeline MCP: plan, write, gate-check, publish, submit, monitor AI visibility.
التثبيت
أضف هذا إلى إعدادات MCP في عميلك (Claude Desktop: claude_desktop_config.json، وCursor: .cursor/mcp.json، ويستخدم VS Code وغيره الصيغة نفسها «mcpServers»).
@tengence/geo-mcpclaude mcp add tengence-geo-agent -e 'SITES_ROOT=<SITES_ROOT>' -e 'TENGENCE_GEO_HOME=<TENGENCE_GEO_HOME>' -e 'DB_DRIVER=<DB_DRIVER>' -- npx -y @tengence/geo-mcp@0.1.2
{
"mcpServers": {
"tengence-geo-agent": {
"command": "npx",
"args": [
"-y",
"@tengence/geo-mcp@0.1.2"
],
"env": {
"SITES_ROOT": "<SITES_ROOT>",
"TENGENCE_GEO_HOME": "<TENGENCE_GEO_HOME>",
"DB_DRIVER": "<DB_DRIVER>"
}
}
}
}
متغيرات البيئة
SITES_ROOTRoot directory holding per-site config and .env files. Optional; the workspace is chosen at runtime via the workspace_use tool.TENGENCE_GEO_HOMEInternal runtime data directory (DB, caches). Defaults to ~/.tengence/geo-mcp.DB_DRIVERStorage backend: sqlite (default) or mysql for production.
التوثيق
مأخوذ من ملف README للمشروع على GitHub ويُحدَّث أسبوعيًا. تفتح الروابط على GitHub.
المحتويات
Tengence GEO Agent
GEO/SEO content production & publishing engine — full-pipeline automation from content planning → writing & ingest → gate checks → WordPress publishing → search submission → GEO monitoring. Three usage modes: CLI / MCP (AI clients) / built-in agent runtime loop. Default storage is a single-file multi-tenant SQLite (auto-initialized) with optional MySQL; designed for open source and multi-site use.
AI clients (any MCP-capable harness)
│ MCP (stdio or Streamable HTTP + Bearer)
▼
@tengence/geo-mcp 29 tools (workspace/site/article/check/publish/plan/image/monitor/db/search/diagnose/util/standards)
▼
@tengence/geo-cli 21 tengence-geo-* commands
▼
@tengence/geo-sdk 15-domain capability layer (site/db/wp/content/images/search/…)
▼
SQLite (auto-init) or MySQL (tengence_geo_*, isolated from prod tengence_omni_*)
Packages (monorepo)
| Package | Form | Description | ||
|---|---|---|---|---|
@tengence/geo-sdk | Library | 15-domain capability layer, lazy-loaded, single require entry | ||
@tengence/geo-cli | CLI | 21 bins (ingest / gate / publish / images / submission / monitor / plan) | ||
@tengence/geo-mcp | MCP Server | 29 tools, stdio + HTTP dual transport, Bearer auth | ||
@tengence/geo-agent | Agent launcher | Runs once DEEPSEEK_API_KEY is set (HARNESS=dsh\ | opencode\ | pi) |
Quick start
npm install
cp -R examples/site-template ~/tengence/sites/my-site
cd ~/tengence/sites/my-site && cp .env.example .env # fill in WP credentials / tokens
# Full CLI pipeline
export SITES_ROOT=~/tengence/sites
tengence-geo-article-ingest hello-geo ./hello-geo.md --site my-site --research ./hello-geo.research.md
tengence-geo-check-article hello-geo --site my-site
# MCP (any MCP-capable client; see docs/mcp-platforms.md)
node packages/geo-mcp/bin/geo-mcp.js # stdio
GEO_MCP_TOKEN=sk-xxx node packages/geo-mcp/bin/geo-mcp-http.js # HTTP
# Agent (runs once the API key is set)
export DEEPSEEK_API_KEY=sk-xxx
npx -y @tengence/geo-agent
Full onboarding: docs/getting-started.md.
Documentation
- Architecture & design decisions (layering / multi-tenancy / init model / why MCP bridging)
- Generic writing & GEO standards — shipped in
@tengence/geo-sdk, consumed via the MCP resourcesgeo://standard-index/geo://standard/{name}and thearticle_drafttool (the requirements an article must satisfy) - Getting started
- MCP integration (stdio / HTTP, any client)
- Release & distribution (npm / Docker)
Development & verification
npm run build # workspace consistency check
npm test # 138 tests (all green on SQLite)
npm run geo:sdk-smoke # SDK smoke test
Security boundaries
- Secrets live only in
SITES_ROOT/<site>/.env(gitignored); the repo ships only the.env.exampletemplate. - The production MySQL (
tengence_omni_*) is never written by this repo; the new repo uniformly usestengence_geo_*. - The MCP HTTP transport requires
GEO_MCP_TOKEN(Bearer).
License
MIT
الأسئلة الشائعة
ما هو Tengence GEO Agent؟
GEO/SEO content pipeline MCP: plan, write, gate-check, publish, submit, monitor AI visibility.
كيف أثبّت Tengence GEO Agent؟
يعمل على جهازك. في Claude Code: claude mcp add tengence-geo-agent -e 'SITES_ROOT=<SITES_ROOT>' -e 'TENGENCE_GEO_HOME=<TENGENCE_GEO_HOME>' -e 'DB_DRIVER=<DB_DRIVER>' -- npx -y @tengence/geo-mcp@0.1.2. وفي العملاء الآخرين، الصق إعداد JSON من هذه الصفحة في إعدادات MCP الخاصة بهم.
هل يحتاج Tengence GEO Agent إلى مفتاح API؟
لا يذكر إدراجه في السجل أي مفتاح أو سر إلزامي. قد تتطلب بعض الميزات حسابًا لدى الخدمة التي يتصل بها.
هل Tengence GEO Agent مفتوح المصدر؟
نعم. شيفرته متاحة على GitHub بترخيص MIT.
من يصون Tengence GEO Agent؟
ينشره tengence-team. يدرجه AI.tn لكنه لا يصونه ولا يوصي به.
من سجل MCP الرسمي. الإدراج ليس توصية: راجع شيفرة الخادم وصلاحياته قبل منحه الوصول إلى بياناتك.