ie-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | Optional GitHub personal access token to increase API rate limits from 60 to 5000 requests/hour. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_installed_package_versionA | Check what version of a package is installed in the MCP server's Python environment. Returns the installed version and the Python executable path so users can verify which environment is being checked. Always call this before get_function_source or get_doc_section when the user has not specified a version, to ensure the documentation and source code match their actual installation. If the package is not installed, the response includes guidance on pointing mcp.json to the right Python environment. Args: package: Package name as returned by list_packages(). |
| get_server_environmentA | Inspect the MCP server's Python environment. Returns the Python executable path, Python version, and the installed version of every package registered in this server. Use this to verify that the MCP server is running in the correct environment before asking about specific packages. If a package shows 'not installed', update the 'command' field in .vscode/mcp.json to point to the Python where you have your packages installed. |
| list_packagesA | List all Python packages that this MCP server has documentation for. |
| get_package_infoA | Get metadata for a package: description, GitHub URL, docs URL, install commands, and the list of available documentation sections. Args: package: Package name as returned by list_packages(). |
| list_doc_versionsA | List all available documentation versions for a package. Queries the ReadTheDocs API to discover published versions. Always call this before get_doc_section or search_docs when the user asks about a specific version other than the latest. Args: package: Package name as returned by list_packages(). |
| get_doc_sectionA | Return the full Markdown content of a specific documentation section. The first call fetches the live docs page and caches it locally. Later calls are served from the cache. Defaults to the latest version. Call list_doc_versions(package) first if the user asks about a specific older version. Call get_package_info(package) first to discover the available sections. Args: package: Package name as returned by list_packages(). section: Section id (e.g. 'introduction', 'faq'). version: Docs version slug (default: 'latest'). Use list_doc_versions() to discover available versions. |
| search_docsA | Search the package documentation for a query string. Missing pages are fetched live and cached before searching. Returns up to 10 matching paragraph-level snippets (case-insensitive). Each result includes the section name and a text snippet (≤500 chars). Defaults to the latest version. Call list_doc_versions(package) first if the user asks about a specific older version. Args: package: Package name as returned by list_packages(). query: Free-text search query. version: Docs version slug (default: 'latest'). Use list_doc_versions() to discover available versions. |
| search_sourceA | Search the GitHub source code of a package for a query string. Uses the GitHub code search API to find files containing the query. Returns up to 10 results with the file name, path, and GitHub URL. Requires the GITHUB_TOKEN environment variable for best results (5000 req/hr authenticated vs 60/hr unauthenticated). Args: package: Package name as returned by list_packages(). query: Search string (e.g. function name, class name, keyword). |
| list_source_versionsA | List all available source code versions (GitHub tags) for a package. Use this when the user asks about a specific version of a function, to confirm the version exists before calling get_function_source. Args: package: Package name as returned by list_packages(). |
| get_function_sourceA | Find a function in the package's GitHub source code and return its full source, including docstring and signature. Searches the repository for files containing the function name, then uses Python's ast module to extract the exact function definition. The raw source file is cached locally after the first fetch. If a version is given, the file is fetched at that GitHub tag. Call list_source_versions(package) first to confirm the version tag exists. Only returns an error if the version tag does not exist, or if the function was not present in the codebase at that version. Args: package: Package name as returned by list_packages(). function_name: Exact name of the function or method to retrieve. version: Optional version tag (e.g. 'v2.1.0' or '2.1.0'). Omit to get the current (latest) implementation. |
| fetch_latest_docsA | Force-fetch documentation for a package directly from the web, bypassing the local cache. Use this when the user wants the most up-to-date content or when cached content may be stale. The fetched page is written to the local cache so later calls are fast. Fetches a specific section page if given, otherwise the docs homepage. Args: package: Package name as returned by list_packages(). section: Optional section id (e.g. 'introduction', 'faq'). Leave empty to fetch the docs homepage. version: Docs version slug (default: 'latest'). Use list_doc_versions() to discover available versions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| get_started | Guide the user through getting started with a package. Fetches installation instructions and the introduction section, then summarises what the package does, how to install it, and a minimal first example. Args: package: Package name (call list_packages() to see available options). |
| explain_function | Explain what a specific function does, including its source and documentation. Fetches the function source from GitHub and searches the docs for relevant context, then explains parameters, return value, and usage. Args: package: Package name (call list_packages() to see available options). function_name: Exact name of the function or method to explain. |
| how_to | Get step-by-step instructions for accomplishing a specific task with a package. Searches the documentation and, if relevant functions are found, fetches their source to produce an accurate, code-level guide. Args: package: Package name (call list_packages() to see available options). task: What you want to accomplish, e.g. 'export a database to SimaPro'. |
| compare_function_versions | Compare how a function changed between two versions of a package. Fetches the function source at both version tags and produces a side-by-side diff with a plain-language explanation of what changed (signature, parameters, logic, docstring, removal). Args: package: Package name (call list_packages() to see available options). function_name: Exact name of the function or method to compare. version_a: First version tag (e.g. 'v1.0.0' or '1.0.0'). version_b: Second version tag to compare against (e.g. 'v2.0.0'). |
| compare_packages | Compare all available packages: what each does and when to choose one over another. Lists all packages, fetches their metadata, and produces a side-by-side summary of purpose, key features, and typical use cases. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/JonasKlimt/ie_mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server