Skip to main content

Documentation Index

Fetch the complete documentation index at: https://superwire.dev/llms.txt

Use this file to discover all available pages before exploring further.

Batch imports reduce repetition when importing several declarations from the same MCP server namespace.

​
Tool-only imports

When the source path ends in .tool, every entry inside the block must be a tool. 
from mcp.tasks.tool {
    tool fetch_task
    tool update_task_status
    tool create_comment
}

​
Prompt-only imports

When the source path ends in .prompt, every entry inside the block must be a prompt. 
from mcp.tasks.prompt {
    prompt fetch_task
    prompt update_task_status
    prompt create_comment
}

​
Resource-only imports

When the source path ends in .resource, every entry inside the block must be a resource. 
from mcp.tasks.resource {
    resource project_readme
    resource task_template
}

​
Mixed imports

When importing from the broader MCP server namespace, the block may contain tools, prompts, and resources. 
from mcp.tasks {
    prompt fetch_task
    tool update_task_status
    resource create_comment
}

​
Shared bindings

A batch import can apply the same bindings to multiple imported tools when those tools need the same trusted runtime values. 
from mcp.tasks.tool {
    bindings {
        workspace_id: input.workspace_id
        project_id: input.project_id
    }

    tool fetch_task
    tool update_task_status
    tool create_comment
}
bindings {} assigns runtime values. It is not a schema declaration.