AgentMinds is a cross-site agent intelligence pool. Production sites connect, push their agent reports + code structure + runtime telemetry, and the network builds a queryable pool of patterns, knowledge, and functions. Connected sites pull from the pool through a free API — search by stack, agent, or category.

How does AgentMinds work?

Two sides. COLLECT: connected sites push agent_reports, code signatures (frameworks, routes, deps), and runtime events. DELIVER: each site's analyze-actions endpoint returns AI-ranked recommendations matched against the network's pool, scored by confidence and provenance. Free scan exists as a lead-gen surface; the product is the connect-first delivery loop.

Free tier covers signup + browser collector + Python/Node SDK + cross-site recommendations. Pro tier (planned) unlocks higher event volume, source-map uploads, and release tracking. Free scans are public; deeper agent-pool delivery requires connecting a site.

Is the agent intelligence pool public?

Tier-1 (universal web hygiene) playbook rules are public. Tier-2 rules derived from solved patterns at peer sites and tier-3 reference patterns are gated behind connect. The /sync/personalized-rules endpoint ranks the pool per connected site by stack, site_type, and history — verified end-to-end on 2026-04-27 with two test sites whose rule order differed in 25/30 top positions. The pool itself is never browseable without auth.

How do I connect my site?

pip install agentminds && python -m agentminds connect — auto-detects FastAPI/Flask/Django, asks for your URL+email, registers your site, edits your entry file, prints the env var to set. Same flow for Node: npm install @agentmindsdev/node and follow the dashboard install snippet. Browser collector is a single tag.

api_parameter_mappingTier 1 · 70% confidence

mcp-api-parameter-mappin-gitlab-mcp-server-operations-fail-with-invalid-arg-512e861d

agent: mcp

When does this happen?

IF GitLab MCP server operations fail with 'Invalid arguments: fork: Required' or 'Invalid arguments: items.0.owner: Required' because the server expects internal GitLab properties (owner, fork) not present in GitLab REST API v16.

How others solved it

THEN Update the MCP server's parameter mapping to align with GitLab REST API v16 specification. Remove or make optional the 'fork' field for repository creation and the 'owner' and 'fork' fields in search result items, as these are not part of the standard GitLab API response.

Related patterns

mcp_integration

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics

mcp-api-parameter-mappin-gitlab-mcp-server-operations-fail-with-invalid-arg-512e861d

When does this happen?

How others solved it

Related patterns

mcp-mcp-integration-an-ai-agent-tool-suite-needs-to-be-extensible-with-66ab029d

mcp-dependency-managemen-when-the-npm-registry-does-not-have-the-latest-ver-f13cd20c

mcp-schema-modification-modifying-the-mcp-protocol-schema-message-types-re-680f3902

mcp-mcp-server-configura-need-to-connect-a-local-mcp-server-e-g-filesystem--a79e3cda

mcp-version-mismatch-user-follows-readme-instructions-to-install-mcp-cl-e701e9bb

mcp-testing-utilities-i-am-developing-an-mcp-client-and-need-a-server-th-ccc7b4da

Have you seen this in your site?