Print env vars avatar
Print env vars

Pricing

Pay per usage

Go to Store
Print env vars

Print env vars

Developed by

Lukáš Křivka

Lukáš Křivka

Maintained by Community

Prints both raw and parsed environment variables provided to each actor run. Stores them to dataset, KV Store and log for easy analysis.

0.0 (0)

Pricing

Pay per usage

2

Total users

3

Monthly users

2

Runs succeeded

>99%

Last modified

7 months ago

You can access the Print env vars programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in Integrations settings in Apify Console.

{
"mcpServers": {
"apify": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.apify.com/sse?actors=lukaskrivka/print-env-vars",
"--header",
"Authorization: Bearer <YOUR_API_TOKEN>"
]
}
}
}

Configure MCP server with Print env vars

You have a few options for interacting with the MCP server:

  • Use mcp.apify.com via mcp-remote from your local machine to connect and authenticate using OAuth or an API token (as shown in the JSON configuration above).

  • Set up the connection directly in your MCP client UI by providing the URL https://mcp.apify.com/sse?actors=lukaskrivka/print-env-vars along with an API token (or use OAuth).

  • Connect to mcp.apify.com via Server-Sent Events (SSE), as shown below:

{
"mcpServers": {
"apify": {
"type": "sse",
"url": "https://mcp.apify.com/sse?actors=lukaskrivka/print-env-vars",
"headers": {
"Authorization": "Bearer <YOUR_API_TOKEN>"
}
}
}
}

You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other MCP client of your choice.

If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.