Skip to content

Update README.md port from 8000 to 8080 #72

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Raibaz merged 2 commits into from
May 8, 2026
+5 −5
Merged

Update README.md port from 8000 to 8080 #72

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9ac0479
Merge pull request #1 from googleads/main
FutureProve May 8, 2026
6ccb349
Update README.md
FutureProve May 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,13 +72,13 @@ To enable it, set the following environment variables:

- `GOOGLE_ADS_MCP_OAUTH_CLIENT_ID`: Your Google Cloud OAuth 2.0 Client ID.
- `GOOGLE_ADS_MCP_OAUTH_CLIENT_SECRET`: Your Google Cloud OAuth 2.0 Client Secret.
- `GOOGLE_ADS_MCP_BASE_URL`: (Optional) The base URL where the server is accessible (defaults to `http://localhost:8000`).
- `GOOGLE_ADS_MCP_BASE_URL`: (Optional) The base URL where the server is accessible (defaults to `http://localhost:8080`).

Once this is enabled, you can authenticate to the API through your MCP client: for example, in Gemini CLI, the command `/mcp auth google-ads-mcp` triggers the authentication flow.

When these variables are set, the server automatically switches to the `streamable-http` transport (SSE/HTTP) instead of `stdio`.

You will need to run the server as a separate process and configure your MCP client to connect to the SSE endpoint (e.g., `http://localhost:8000/mcp`).
You will need to run the server as a separate process and configure your MCP client to connect to the SSE endpoint (e.g., `http://localhost:8080/mcp`).

#### Option 2: Configure credentials using Application Default Credentials

Expand Down Expand Up @@ -151,14 +151,14 @@ popular clients.

- Option 1: Using FastMCP OAuth Proxy (Streamable HTTP)

You can run the server as a separate process and configure your MCP client to connect to the SSE endpoint (e.g., `http://localhost:8000/mcp`).
You can run the server as a separate process and configure your MCP client to connect to the SSE endpoint (e.g., `http://localhost:8080/mcp`).
This also allows using FastMCP's [OAuth proxy](https://gofastmcp.com/servers/auth/oauth-proxy) feature for dynamic user authentication.

```json
{
"mcpServers": {
"google-ads-mcp": {
"httpUrl":"http://localhost:8000/mcp",
"httpUrl":"http://localhost:8080/mcp",
"env": {
"GOOGLE_PROJECT_ID": "YOUR_PROJECT_ID",
"GOOGLE_ADS_DEVELOPER_TOKEN": "YOUR_DEVELOPER_TOKEN"
Expand Down Expand Up @@ -378,4 +378,4 @@ While that guide is specific to Gemini CLI, Agent Skills are an open standard an

## Contributing

Contributions welcome! See the [Contributing Guide](CONTRIBUTING.md).
Contributions welcome! See the [Contributing Guide](CONTRIBUTING.md).
Loading