Skip to content

Structured MCP call outcome for hosts, and OAuth/config_doc follow-ups to #39 #40

Description

@oxoxDev

Summary

Let a host observe every MCP bridge call without wrapping the tool, plus small follow-ups to the host-backed OAuth flow (#39), so OpenCompany can drop its own call wrapper and OAuth port.

Scope

  • tinymcp-bus: McpCallOutcome / McpCallError + MCP_CALL_RESULT_KIND; McpCallTool sets it as ToolResult.metadata on success and on errors once server and tool are known.
  • OAuth: public OAuthBundle; OAuthFlow::refresh that re-applies the public-endpoint guard.
  • config_doc: parse_with (registered host fields, lenient mode) and render symmetry for allowed_tools, disallowed_tools, timeout_secs.
  • SecretScrubber::with_secrets for host-known secrets.

Acceptance

fmt / clippy / tests / 90% per-file coverage green; bus serde round-trips; OpenHuman and OpenCompany compile against the branch.

Activity

  1. self-assigned this
    on Oct 6, 2026
  2. tinysweeper commented on Oct 6, 2026

    @tinysweeper

    Feature request: expose structured MCP call outcomes (McpCallOutcome/McpCallError) so hosts can observe bridge calls without wrapping tools, plus follow-ups to the host-backed OAuth flow (OAuthBundle, OAuthFlow::refresh), config_doc parse_with and render symmetry, and SecretScrubber::with_secrets. Enhancement work with acceptance criteria tied to fmt/clippy/tests/coverage and downstream consumers compiling.

    Labelled priority: p3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions