OSF CLI Go
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OSF_TOKEN | No | Personal access token for OSF authentication. | |
| OSF_PASSWORD | No | OSF password for fallback authentication. | |
| OSF_USERNAME | No | OSF username for fallback authentication. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| osf_components_listA | List immediate child components for an OSF project or component. |
| osf_contributors_listC | List contributors for an OSF project or component. |
| osf_files_listB | List OSF Storage files and folders for a project/component, optionally below a path. |
| osf_project_getB | Get an OSF project or component by id or URL. |
| osf_projects_listA | List projects owned by the authenticated OSF user. |
| osf_whoamiA | Return the authenticated OSF user profile. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct resource (components, contributors, files, project, projects list, user profile) with no overlapping purposes, making it easy for an agent to select the correct tool.
All tools share the 'osf_' prefix and use snake_case, generally following a 'noun_list' or 'noun_get' pattern. The exception is 'osf_whoami', which deviates slightly, but overall consistency is high.
With 6 tools, the server is well-scoped for basic OSF query operations. The count is appropriate for the focused read-only functionality offered.
The tool set covers read operations (list, get) for core OSF entities but lacks write, update, or delete actions, leaving obvious gaps for a full lifecycle. Agents can query but not modify data.