I am getting some parsing errors.

[regismesquita]

O3-mini for models and Haiku on claude desktop

[regismesquita]

huh, tried again with Sonnet and 4o and it worked, on the previous research it tried using the write_report tool which caused the issue, now it wrote the research directly.

[assafelovic]

Great! How is it for you?

[regismesquita]

Very nice, I also have the tavily mcp, here is a comparison of both on a recent query of mine.

When comparing the deep research results with the regular search, I found several key differences and similarities:
Similarities

Address Information: Both methods correctly identified the NCT Test Center's location as Deansgrange Bus Park, Dublin, A94 K402.
Basic Contact Information: Both found the main contact phone number (01 413 5992), though the deep research provided more context about hours when phone support is available.
Opening Hours Structure: Both found that the center has varying hours by day of the week and is typically closed on Sundays.

Key Differences

Depth of Information:

The regular search only provided the scheduled hours for the upcoming week
The deep research uncovered multiple sources showing different "regular" operating hours patterns, revealing inconsistencies across websites


Alternative Contact Methods:

The deep research found booking email addresses and customer service contact information that wasn't found in the regular search


Additional Context:

The deep research included customer reviews and experiences
The deep research uncovered nearby businesses and services related to car testing/repairs
The deep research revealed different phone numbers listed on different platforms


Discrepancies Identified:

The deep research highlighted contradictions between sources, particularly about Sunday hours (official site shows closed while some third-party sites showed open)
The deep research revealed variations in listed regular operating hours between different sources


Reliability Assessment:

The deep research allowed for identifying the most authoritative source (official NCTS website) compared to third-party information
The deep research provided more context about the booking process and system



In summary, while the regular search provided accurate basic information from the official source, the deep research offered a more comprehensive picture with multiple perspectives, identified inconsistencies across sources, and provided additional context that would be valuable for someone planning to use the service. The deep research also helped distinguish between current/specific opening times for upcoming dates versus the "regular" pattern of opening hours.

The write_report tool is indeed broken though :(

[regismesquita]

Error Logs

2025-04-11T10:54:26.470Z [gptr] [error] Unexpected token '�', "🚀 GPT Res"... is not valid JSON {"context":"connection","stack":"SyntaxError: Unexpected token '\ud83d', \"🚀 GPT Res\"... is not valid JSON\n    at JSON.parse (<anonymous>)\n    at F$e (/Applications/Claude.app/Contents/Resources/app.asar/.vite/build/index.js:108:189)\n    at j$e.readMessage (/Applications/Claude.app/Contents/Resources/app.asar/.vite/build/index.js:108:115)\n    at B$e.processReadBuffer (/Applications/Claude.app/Contents/Resources/app.asar/.vite/build/index.js:109:1842)\n    at Socket.<anonymous> (/Applications/Claude.app/Contents/Resources/app.asar/.vite/build/index.js:109:1523)\n    at Socket.emit (node:events:518:28)\n    at addChunk (node:internal/streams/readable:561:12)\n    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)\n    at Readable.push (node:internal/streams/readable:392:5)\n    at Pipe.onStreamRead (node:internal/stream_base_commons:191:23)"}
INFO:     [11:54:26] 📝 Report written for 'NCT Test Center in Dun Laoghaire or Deansgrange opening hours, address and contact information'
2025-04-11T10:54:26.470Z [gptr] [error] Unexpected token 'E', "Error pars"... is not valid JSON {"context":"connection","stack":"SyntaxError: Unexpected token 'E', \"Error pars\"... is not valid JSON\n    at JSON.parse (<anonymous>)\n    at F$e (/Applications/Claude.app/Contents/Resources/app.asar/.vite/build/index.js:108:189)\n    at j$e.readMessage (/Applications/Claude.app/Contents/Resources/app.asar/.vite/build/index.js:108:115)\n    at B$e.processReadBuffer (/Applications/Claude.app/Contents/Resources/app.asar/.vite/build/index.js:109:1842)\n    at Socket.<anonymous> (/Applications/Claude.app/Contents/Resources/app.asar/.vite/build/index.js:109:1523)\n    at Socket.emit (node:events:518:28)\n    at addChunk (node:internal/streams/readable:561:12)\n    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)\n    at Readable.push (node:internal/streams/readable:392:5)\n    at Pipe.onStreamRead (node:internal/stream_base_commons:191:23)"}
2025-04-11T10:54:26.470Z [gptr] [error] Unexpected token 'E', "Error! : H"... is not valid JSON {"context":"connection","stack":"SyntaxError: Unexpected token 'E', \"Error! : H\"... is not valid JSON\n    at JSON.parse (<anonymous>)\n    at F$e (/Applications/Claude.app/Contents/Resources/app.asar/.vite/build/index.js:108:189)\n    at j$e.readMessage (/Applications/Claude.app/Contents/Resources/app.asar/.vite/build/index.js:108:115)\n    at B$e.processReadBuffer (/Applications/Claude.app/Contents/Resources/app.asar/.vite/build/index.js:109:1842)\n    at Socket.<anonymous> (/Applications/Claude.app/Contents/Resources/app.asar/.vite/build/index.js:109:1523)\n    at Socket.emit (node:events:518:28)\n    at addChunk (node:internal/streams/readable:561:12)\n    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)\n    at Readable.push (node:internal/streams/readable:392:5)\n    at Pipe.onStreamRead (node:internal/stream_base_commons:191:23)"}
2025-04-11T10:54:26.471Z [gptr] [error] Unexpected token '�', "�[32m# **N"... is not valid JSON {"context":"connection","stack":"SyntaxError: Unexpected token '\u001b', \"\u001b[32m# **N\"... is not valid JSON\n    at JSON.parse (<anonymous>)\n    at F$e (/Applications/Claude.app/Contents/Resources/app.asar/.vite/build/index.js:108:189)\n    at j$e.readMessage (/Applications/Claude.app/Contents/Resources/app.asar/.vite/build/index.js:108:115)\n    at B$e.processReadBuffer (/Applications/Claude.app/Contents/Resources/app.asar/.vite/build/index.js:109:1842)\n    at Socket.<anonymous> (/Applications/Claude.app/Contents/Resources/app.asar/.vite/build/index.js:109:1523)\n    at Socket.emit (node:events:518:28)\n    at addChunk (node:internal/streams/readable:561:12)\n    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)\n    at Readable.push (node:internal/streams/readable:392:5)\n    at Pipe.onStreamRead (node:internal/stream_base_commons:191:23)"}
2025-04-11T10:54:26.471Z [gptr] [error] Unexpected end of JSON input {"context":"connection","stack":"SyntaxError: Unexpected end of JSON input\n    at JSON.parse (<anonymous>)\n    at F$e (/Applications/Claude.app/Contents/Resources/app.asar/.vite/build/index.js:108:189)\n    at j$e.readMessage (/Applications/Claude.app/Contents/Resources/app.asar/.vite/build/index.js:108:115)\n    at B$e.processReadBuffer (/Applications/Claude.app/Contents/Resources/app.asar/.vite/build/index.js:109:1842)\n    at Socket.<anonymous> (/Applications/Claude.app/Contents/Resources/app.asar/.vite/build/index.js:109:1523)\n    at Socket.emit (node:events:518:28)\n    at addChunk (node:internal/streams/readable:561:12)\n    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)\n    at Readable.push (node:internal/streams/readable:392:5)\n    at Pipe.onStreamRead (node:internal/stream_base_commons:191:23)"}

[hstaudacher]

I'm running into the same issue.

[regismesquita]

@hstaudacher I was able to make it work but endup never pushing a fix. There are some colors characters that cause the write_report function to break the MCP communication over STDIO. (also not sure if this is the repo to use, maybe we need to use the main one)

[regismesquita]

@assafelovic should I open PR's to this repo or to the main one at https://github.com/assafelovic/gpt-researcher/tree/master/mcp-server ?

[hstaudacher]

Thanks for the hint and the PR offer @regismesquita

[hstaudacher]

@regismesquita I think the main one is the correct one. It seems @assafelovic is doing active development there, see assafelovic/gpt-researcher#1395

[assafelovic]

just to clarify @hstaudacher there are two MCP developments:

• MCP Server: this one - exposing GPTR as a tool
• MCP Client: Enabling GPTR itself to conduct research with mcp servers which is what you're referring to.

I will continue to investigate the docker issue and update