
ASTGL Knowledge
io.github.Jmeg8rPublished by GitHub account Jmeg8rv1.3.1Updated Oct 25, 2026
Search and cite ASTGL articles about MCP servers, local AI, and AI automation.
Overview
A local MCP server that lets an assistant search, compare and cite ASTGL articles on MCP servers, local AI and AI automation.
- What you can do
- Search the ASTGL knowledge base and get ranked results with source links, or ask a question for a direct answer drawn from FAQ entries. Pull step-by-step tutorials and guides, and compare two topics side by side. Browse the index by tag, content type, title text or date range, and list topics, tags and the latest additions. Export articles, topic roundups and Q&A compilations as markdown, and keep an idea journal with suggestions from query analytics.
- When to use it
- Useful when you want an assistant to ground answers about MCP servers, local AI setup or automation in ASTGL's published material and cite the sources, rather than relying on general knowledge.
- Requirements
- Runs locally via npx, so Node.js is needed. The semantic tools (search, answer, tutorial, comparison) also need a local Ollama instance serving the nomic-embed-text model; the metadata tools work without it. An optional ASTGL_API_KEY raises the daily query limit.
Installation
In SourceWeft
- Open ASTGL Knowledge in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
mcp-astgl-knowledge
An MCP server that lets AI assistants search and cite content from As The Geek Learns — covering MCP servers, local AI, AI automation, and ASTGL project documentation.
When an AI assistant connects to this server, it can search the indexed ASTGL entries (articles, tutorials, comparisons, guides, and project docs). Search results include source URLs back to astgl.ai.
Requirement: the semantic tools (
search_articles,get_answer,get_tutorial,compare_topics) embed your query at runtime with a local Ollama runningnomic-embed-text(defaulthttp://localhost:11434). The metadata tools (find_articles,list_tags,list_topics,get_latest) work without Ollama.
Quick Start
Claude Desktop
Add to your claude_desktop_config.json:
Claude Code
Add to your project's .mcp.json:
Cursor / Generic MCP Client
With Registration (500 queries/day)
Register via the register tool to get an API key, then add it to your config:
Tools
search_articles
Search the knowledge base by query. Returns ranked results with relevance scores and source URLs.
get_answer
Get a direct answer to a specific question. Prefers FAQ entries for concise responses.
get_tutorial
Get step-by-step instructions from tutorial and guide content.
compare_topics
Side-by-side comparison of two topics.
get_latest
Get the most recently added content.
list_topics
Browse all topics in the knowledge base with content types and section headings.
register
Register your email to unlock 500 queries/day (up from 50).
More tools
The server registers 17 tools in total. The others:
Content Types
Counts change as content is added; call list_topics or list_tags for the current index.
draft and synthesis entries exist only in the maintainer database and are removed from the
published one. The content_type descriptions in the tool schemas list only the first seven types.
Rate Limits
Limits reset at midnight UTC. Rate limit info is included in every response.
Limits and registrations are enforced by the server process itself: usage and registrations are kept in a local SQLite file (data/query-log.db next to the package, or ASTGL_QUERY_LOG_DB), and anonymous clients get a persistent ID in ~/.astgl-client-id. An ASTGL_API_KEY only counts as registered if it exists in that local registrations table.
How It Works
The knowledge base is pre-built from ASTGL articles using semantic embeddings (nomic-embed-text, 768 dimensions). Content is chunked by section and FAQ entry, embedded, and stored in a SQLite database with sqlite-vec for vector similarity search.
Article embeddings are pre-computed and shipped in the npm package, so you never re-index content. Your query is still embedded at runtime through Ollama for the semantic tools (see the requirement above).
The server opens data/knowledge.db when it exists (a maintainer checkout) and otherwise build/knowledge-public.db. The npm package ships only build/knowledge-public.db, which npm run build-public-db produces by physically removing every non-public row (see docs/adr/).
Performance
- Typical response time: 100-500ms (embedding lookup + vector search)
- Embedding results are cached in memory (LRU, 200 entries) — repeated queries are near-instant
- Ollama calls include 10s timeout + automatic retry
- Query logging is async/batched to avoid blocking responses
- Rate limit checks are cached for 5 seconds
For Maintainers
Setup
Scripts
Other maintainer scripts (draft ingest and reconcile, rewrite queue, wiki sync, backup pruning, dashboard data, MCPB bundle) are listed in package.json.
Environment Variables
Automated Jobs
Schedules are defined in cron/*.json; the scheduled report jobs print JSON that an external scheduler picks up and delivers. Run the report scripts with --discord to post to DISCORD_WEBHOOK_URL instead. macOS launchd plists for the pipeline, draft and wiki jobs are in launchd/.
Architecture
A rendered diagram is in docs/diagrams/mcp-astgl-knowledge.architecture.svg
(source: docs/diagrams/mcp-astgl-knowledge.architecture.json).
License
MIT
Source: README.md at commit 262bc4c
Tools
0Version history
1- v1.3.1LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.