MCP Element Discovery is no being cached?

[eyalCanditech]

Hi,

I suspect that MCP element discovery caching is not working well in our setup.
Looks like it is running more than it should, upon every MCP request. (I see many "Starting MCP element discovery..." messages in our logs).
I suspect that it is not being cached correctly and therefore, cause delays.
I am using "http_integrated" mode, and Redis caching.

Any pointers on how I can troubleshoot this further can help!

I have got this mcp.php config out of tinker (replaced my actual folder with "[my_project_path]"):

config('mcp')
= [
"server" => [
"name" => "Laravel MCP",
"version" => "1.0.0",
"instructions" => null,
],
"discovery" => [
"base_path" => "[my_project_path]",
"directories" => [
"app/Mcp",
"app/Services",
],
"exclude_dirs" => [
"vendor",
"tests",
"storage",
"public",
"resources",
"bootstrap",
"config",
"database",
"routes",
"node_modules",
".git",
],
"definitions_file" => "[my_project_path]/routes/mcp.php",
"auto_discover" => true,
"save_to_cache" => true,
],
"cache" => [
"store" => "redis",
],
"transports" => [
"stdio" => [
"enabled" => false,
],
"http_dedicated" => [
"enabled" => false,
"legacy" => false,
"host" => "127.0.0.1",
"port" => 8090,
"path_prefix" => "mcp",
"ssl_context_options" => [],
"enable_json_response" => true,
"event_store" => null,
],
"http_integrated" => [
"enabled" => true,
"legacy" => false,
"route_prefix" => "mcp",
"middleware" => [
"mcp",
],
"domain" => null,
"sse_poll_interval" => 1,
"cors_origin" => "*",
"enable_json_response" => true,
"event_store" => null,
],
],
"session" => [
"driver" => "cache",
"ttl" => 3600,
"store" => "redis",
"path" => "[my_project_path]/storage/framework/mcp_sessions",
"connection" => "mysql",
"table" => "mcp_sessions",
"lottery" => [
2,
100,
],
],
"pagination_limit" => 50,
"capabilities" => [
"tools" => true,
"toolsListChanged" => false,
"resources" => false,
"resourcesSubscribe" => false,
"resourcesListChanged" => false,
"prompts" => false,
"promptsListChanged" => false,
"logging" => false,
"completions" => false,
"experimental" => null,
],
"logging" => [
"channel" => "stack",
"level" => "warning",
],
]

[CodeWithKyrian]

From your config, discovery.auto_discover is set to true, which means MCP element discovery will run on every app boot. That’s the expected behavior, especially useful during development when you're frequently changing elements.

If you're in production or want to avoid the repeated discovery, you can safely turn off auto_discover by setting it to false. Just make sure to manually run:

php artisan mcp:discover

during deploys or whenever you make changes to your MCP elements. That way, they get cached properly, and discovery won’t re-run on every request.