googleapis/mcp-toolbox · error
invalid source for %q tool: source %q is not a compatible ty
Error message
invalid source for %q tool: source %q is not a compatible type
What it means
This error is thrown by the postgres-list-tablestats tool's ValidateSource method when the source named in the tool's YAML config does not implement the tool's `compatibleSource` interface (a Postgres-backed source exposing a pgx pool). MCP Toolbox tools are decoupled from concrete source types, so at startup each tool type-asserts its configured source; the assertion failing means the tool was wired to a source it cannot use.
Source
Thrown at internal/tools/postgres/postgreslisttablestats/postgreslisttablestats.go:179
resp, err := source.RunSQL(ctx, listTableStats, sliceParams)
if err != nil {
return nil, util.ProcessGeneralError(err)
}
return resp, nil
}
func (t Tool) GetSourceName() string {
return t.Cfg.Source
}
func (t Tool) ToConfig() tools.ToolConfig {
return t.Cfg
}
func (t Tool) ValidateSource(source sources.Source) error {
_, ok := source.(compatibleSource)
if !ok {
return fmt.Errorf("invalid source for %q tool: source %q is not a compatible type", t.Cfg.Type, t.Cfg.Source)
}
return nil
}
View on GitHub (pinned to 8cc6e09de2)
Solutions
- Change the tool's `source:` field to the name of a Postgres source defined in `sources:`
- Verify the source kind (e.g. `postgres`) implements the interface the tool requires
- Validate the config locally before deploying
Example fix
# before kind: postgres-list-tablestats source: my-mysql-source # after kind: postgres-list-tablestats source: my-postgres-source
Defensive patterns
Strategy: validation
Validate before calling
if _, ok := any(myPostgresSource).(interface {
PostgresPool() *pgxpool.Pool
RunSQL(context.Context, string, []any) (any, error)
}); !ok {
log.Fatalf("source is not compatible with postgres-list-tablestats")
} Type guard
func isCompatiblePostgresSource(s sources.Source) bool {
_, ok := s.(interface {
PostgresPool() *pgxpool.Pool
RunSQL(context.Context, string, []any) (any, error)
})
return ok
} Prevention
- Match tool kind prefix to source kind (postgres-* -> kind: postgres)
- Validate tools.yaml in CI with the toolbox binary
- Grep tools.yaml for `source:` values after renaming sources
- Keep one canonical source per engine to reduce mismatches
When it happens
Trigger: Server startup/config validation when a tool of `kind: postgres-list-tablestats` references a `source:` whose registered source does not satisfy the compatibleSource interface (e.g. a non-Postgres source like redis, mysql, http).
Common situations: Copy-pasted tool entries with stale `source:` names; pointing Postgres tools at MySQL/Cloud SQL MySQL sources; typos that resolve to a differently-typed source.
Related errors
- invalid source for %q tool: source %q is not a compatible ty
- invalid source for %q tool: source %q is not a compatible ty
- invalid source for %q tool: source %q is not a compatible ty
- invalid source for %q tool: source %q is not a compatible ty
- invalid source for %q tool: source %q is not a compatible ty
AI-assisted analysis of googleapis/mcp-toolbox@8cc6e09de2 (2026-09-05).
Data as JSON: /api/errors/9d5efee4a2826413.
Report an issue: GitHub.