pod
Other formats agents might prefer:
markdownjsonllms.txt

Agent? You probably want markdown or json, or Pod over MCP.

Reported issues for OSF CLI Go

Pod holds 13 of 13 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to OSF CLI Go.

Most discussed

Freeze OSF API and CLI/MCP compatibility contracts for 1.0

Follow-up to the prepared OSF API schema discovery issue #46 and closed launch issue #52.\n\nTurn the prepared schema and existing CLI/MCP contracts into an explicit 1.0 compatibility boundary.\n\nAcceptance:\n- The pinned OSF API source, license, retrieval date, and commit are reviewed and recorded.\n- Generated or vendored schema decisions are documented.\n- CLI JSON, MCP tool names, input schemas, output schemas, errors, limits, and authentication behavior have golden compatibility fixtures.\

Read the thread · 2026-07-14 · closed · 6 comments

Run live OSF validation for the v1.0 release candidate

Follow-up to the existing opt-in live validation track and closed launch issue #52.\n\nExecute the release-candidate validation against a disposable OSF project using a scoped credential, without committing or exposing secrets.\n\nAcceptance:\n- Authentication, identity, projects, components, files, search, preprints, downloads, uploads, conflicts, cancellation, and MCP tools are exercised as applicable.\n- Any write tests use a disposable project and clean up safely.\n- Sanitized evidence recor

Read the thread · 2026-07-14 · closed · 4 comments

Define and implement structured observability for 1.0

Follow-up to the 1.0 launch review and closed hardening issue #52.\n\nDefine a stable structured logging and operational event contract for CLI, API, transfers, and MCP execution.\n\nAcceptance:\n- JSON events include operation/request IDs, duration, retry count, outcome, and classified errors.\n- Human-readable stderr remains usable and machine-readable output is not polluted.\n- OSF tokens, passwords, authorization headers, local secrets, and sensitive paths are redacted.\n- Logging levels, ou

Read the thread · 2026-07-14 · closed · 4 comments

Submit OSF MCP server to LobeHub MCP Marketplace

Prepare and submit the owned repository to LobeHub MCP Marketplace (https://market.lobehub.com/s/publish-mcp) using the official @lobehub/market-cli. Add and validate lhm.plugin.json, connect GitHub ownership and authenticate in-browser when required, publish a release-aligned version, and record the public listing URL. Do not expose marketplace credentials.

Read the thread · 2026-07-13 · closed · 4 comments

Submit OSF MCP server to Cline MCP Marketplace

Prepare and submit https://github.com/edithatogo/osf-cli-go to the official Cline MCP Marketplace. Requirements include a 400x400 PNG logo, reason for addition, and validation that Cline can install from README.md or llms-install.md. Record the submission issue URL and review status; do not claim approval until the upstream repository reflects it.

Read the thread · 2026-07-13 · closed · 4 comments

Add Zenodo provider support and a shared OSF/Zenodo research repository model

Objective

Add an opt-in Zenodo provider and a provider-neutral research repository layer so the CLI and MCP server can support comparable OSF and Zenodo workflows without flattening provider-specific safety or metadata semantics.

Scope

  • Map the official Zenodo REST API: records, depositions, files, DOI reservation/publication, authentication scopes, rate limits, sandbox, and OAI-PMH discovery.
  • Define a provider-neutral artifact, record, file, metadata, identifier, and transfer model

Read the thread · 2026-07-14 · closed · 3 comments

Expose provider-scoped MCP tools and compatibility fixtures

Parent epic: #101

Scope

  • Add Zenodo read-only MCP tools or provider arguments aligned with the reviewed domain contract.
  • Add capability discovery and stable schemas for agents.

Acceptance criteria

  • MCP fixtures cover negotiation, success, unsupported operations, errors, and redaction.
  • Existing OSF MCP tool contracts remain compatible.
  • Registry metadata does not advertise unimplemented Zenodo writes.

Read the thread · 2026-07-14 · closed · 2 comments

Evaluate additional MCP registries and agent marketplaces

Assess current submission paths for MCP.so, mcpservers.org, MCPize, MCP Market, LobeHub, Cline, Docker MCP Catalog, PulseMCP, MCP Central, and any newly credible registry. Classify each as public submission, account/auth required, inaccessible, deprecated, or not worth pursuing. Record source URLs, requirements, and exact next actions without treating a prepared packet as a submission or approval.

Read the thread · 2026-07-13 · closed · 2 comments

Most recent

Expand OSF API entity coverage

Track the remaining read-only OSF API coverage gaps in the feature matrix: file versions, add-ons, wiki pages, comments, logs, and identifiers. Keep CLI/API/MCP contracts typed, deterministic, and offline-tested before marking rows implemented.

Read the thread · 2026-07-13 · closed · 1 comment

Add MCP tool quality and compatibility evaluation harness

Build a repeatable offline and opt-in live harness that checks tool schemas, descriptions, structured output, error/redaction behavior, pagination/limits, latency/resource bounds, client configuration compatibility, and registry metadata consistency. Produce versioned reports suitable for release and marketplace submissions.

Read the thread · 2026-07-13 · closed · 1 comment

Build comprehensive OSF CLI/MCP feature matrix

Create and maintain a source-backed matrix covering OSF entities, CLI commands, API client methods, MCP tools, auth modes, read/write safety, output formats, pagination, downloads, registries, and competitor parity tracks. Every row must be implemented, explicitly deferred, rejected with rationale, or linked to a track. Include dated evidence and release-version alignment.

Read the thread · 2026-07-13 · closed · 0 comments

Complete a high-value MCP registry and catalog sweep

Objective\n\nSubmit or verify OSF CLI Go in Docker MCP Catalog, mcp.so, awesome-mcp-servers, PulseMCP, MCP.Directory, MCPize or current equivalents, prioritizing authoritative and maintained surfaces.\n\n## Acceptance criteria\n\n- [ ] Record authoritative current requirements and submission URLs.\n- [ ] Separate repository-local readiness from provider review, authentication, and approval gates.\n- [ ] Add tests or reproducible validation where applicable.\n- [ ] Preserve security, licensing

Read the thread · 2026-07-11 · closed · 2 comments

Package and publish OSF integrations for additional coding agents

Objective\n\nAudit Cursor, Cline, Roo Code, Windsurf, VS Code, Zed, and other MCP/plugin-capable coding agents; create native packages or verified install recipes and submit where public galleries exist.\n\n## Acceptance criteria\n\n- [ ] Record authoritative current requirements and submission URLs.\n- [ ] Separate repository-local readiness from provider review, authentication, and approval gates.\n- [ ] Add tests or reproducible validation where applicable.\n- [ ] Preserve security, licens

Read the thread · 2026-07-11 · closed · 2 comments

The remaining reports are on the project's issue tracker.